High bandwidth broadcast system having localized multicast access to broadcast content

ABSTRACT

A method and arrangement is provided for the multicasting of streaming digital content to a plurality of Internet users. Streaming digital audio, video or other digital data content that is to be multicast to Internet users is formatted into IP protocol at a head-end content source transmission site. The streaming IP digital data is transmitted from the head-end transmission site to at least one distant/remote routing station of an Internet service provider (i.e., a provider-edge router or Internet point of presence) via a bandwidth portion of a digital communications data transport service or transmission medium that is substantially unaffected by conventional Internet communications traffic. The Internet service provider (ISP) maintains at least one access router for providing Internet access via its Internet domain for its customers accessing the Internet via conventional two-way IP connection. The streaming IP digital data received from the content source transmission site by the ISP routing station may then be multicast via the IPS&#39;s existing infrastructure to one or more of its Internet access customer.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of application Ser. No.09/805,686, filed Apr. 19, 2000, now U.S. Pat. No. 6,411,616, which is acontinuation of application Ser. No. 08/969,164, filed Nov. 12, 1997,now U.S. Pat. No. 6,101,180. In addition to being related to parentapplication Ser. No. 09/805,686, this continuation case is also relatedto the following continuation application (which also claims the benefitof priority from the Ser. No. 08/969,164 common parent application):Ser. No. 09/772,958, filed Jan. 31, 2001, entitled “High BandwidthBroadcast System Having Localized Multicast Access to Broadcast Content”The present application also claims priority from related provisionalapplications: U.S. Ser. No. 60/029,427, filed Nov. 12, 1996; U.S. Ser.No. 60/039,672, filed Feb. 28, 1997; and U.S. Ser. No. 60/057,857, filedSep. 2, 1997; all of the provisional applications are now abandoned.

BACKGROUND OF THE INVENTION

During the 1970's and 1980's, the defense industry encouraged anddeveloped an interconnecting network of computers as a backup fortransmitting data and messages in the event that established traditionalmethods of communication fails. University mainframe computers werenetworked in the original configurations, with many other sources beingadded as computers became cheaper and more prevalent. With a looseinterconnection of computers hardwired or telephonically connectedacross the country, the defense experts reasoned that many alternativepaths for message transmission would exist at any given time. In theevent that one message path was lost, an alternative message path couldbe established and utilized in its place. Hence, it was the organizedand non-centralized qualities of this communications system which madeit appealing to the military as a backup communication medium. If anyone computer or set of computers was attacked or disconnected, manyother alternative paths could eventually be found and established.

This interconnection of computers has since been developed byuniversities and businesses into a worldwide network that is presentlyknown as the Internet. The Internet, as configured today, is a publiclyaccessible digital data transmission network which is primarily composedof terrestrial communications facilities. Access to this worldwidenetwork is relatively low cost, and hence, it has become increasinglypopular for such tasks as electronic mailing and weather page browsing.Both such functions are badge or file transfer oriented. Electronicmail, for instance, allows a user to compose a letter and transmit itover the Internet to an electronic destination. For Internet transfers,it s relatively unimportant how long each file transfer takes as long asit is reasonable. The Internet messages are routed, not through a fixedpath, but rather through various interconnected computers until theyhave reached their destination. During heavy message load periods,messages will be held at various internal network computers until thepathways cleared for new transmissions. Accordingly, Internettransmissions are effective, but cannot be relied upon for timesensitive applications.

Web pages are collections of data including text, audio, video, andinterlaced computer programs. Each web page has a specific electronicsite destination which is accessed through a device known as a webserver, and can be accessed by anyone through via Internet. Web pagebrowsing allows a person to inspect the contents of a web page on aremote server to glean various information contained therein, includingfor instance product data, company backgrounds, and other suchinformation which can be digitized. The remote server data is access bya local browser, and the information is displayed as text, graphics,audio, and video.

The web browsing process, therefore, is a two-way data communicationbetween the browsing user, who has a specific electronic address ordestination, and the web page, which also has a specific electronicdestination. In this mode of operation, as opposed to electronic mailfunctions, responsiveness of the network is paramount since the userexpects a quick response to each digital request. As such, each browsinguser establishes a two-way data communication, which ties up an entiresegment of bandwidth on the Internet system.

Recent developments on the Internet include telephone, video phone.conferencing and broadcasting applications. Each of these technologiesplaces a similar real-time demand on the Internet. Real-time Internetcommunication involves a constant two-way throughput of data between theusers and the data must be received by each user nearly immediatelyafter its transmission by the other user. However, the original designof the Internet to did not anticipate such real-time data transmissionrequirements. As such, these new applications have serious technicalhurdles to overcome in order to become viable.

Products which place real-time demands on the Internet will be aided bythe introduction of an updated hardware interconnection configurationsor backbone,” which provides wider bandwidth transmission capabilities.For instance, the MCI backbone was recently upgraded to 622 megabytesper second. Regardless of such increased bandwidth, the interconnectionconfiguration is comprised of various routers which may still not befast enough and can therefore significantly degrade the overallend-to-end performance of the traffic on the Internet. Moreover, evenwith a bandwidth capability of 622 megabytes per second, the Internetbackbone can maximally carry only the following amounts of data: 414-1.5mbs data streams; 4,859-128 kbs data streams; 21597-28.8 kbs datastreams; or combinations thereof. While this has anticipated as beingsufficient by various Internet providers, it will quickly prove to beinadequate for near-future applications.

Internal networks, or Intranet sites, might also be used for datatransfer and utilize the same technology as the Internet. Intranets,however, are privately owned and operated and are not accessible by thegeneral public. Message and data traffic in such private networks isgenerally much lower than more crowded public networks. Intranets aretypically much more expensive for connect time, and therefore anyrelated increase in throughput comes at a significantly higher price tothe user.

To maximize accessibility of certain data, broadcasts of radio shows,sporting events, and the like are currently provided via Internetconnections whereby the broadcast is accessible through a specific webpage connection. However, as detailed above, each web page connectionrequires a high throughput two-way connection through the standardInternet architecture. A given Internet backbone will be quicklyoverburdened with users if the entire set of potential broadcastersacross world began to provide broadcast services via such web pageconnections. Such broadcast methods through the Internet thereby proveto be ineffective given the two-way data throughput needed to access webpages and real-time data.

Furthermore, broadcasts are typically funded and driven by advertisingconcerns. However, a broadcast provided through a centralized location,such as a web page for a real-time Internet connection, will be limitedby practical concerns to offering only nationally advertised products,such as Coke or Pepsi. Since people might be connected to this web pagefrom around the world, local merchants would have little incentive topay to advertise to distant customers outside of their marketing area.Local merchants, on the other hand, would want to inject their localadvertising into the data transmission or broadcasts in such a way notcurrently available on the Internet.

There is an enormous demand for the delivery of large amounts of contentto a large number of listeners. The broadcast channels of today, such asradio and TV, can only deliver a small number of channels to a largenumber of listeners. Their delivery mechanism is well known tocustomers. The broadcaster transmits programs and the listener must tunein” at the proper time and channel to receive the desired show, “OnDemand’ systems have been attempted by the cable industry. Such systemsattempt to transport the program or show from a central repository(server) to the user (client) in response to his/her request. Toinitiate the request, the user selects from a list of candidate programsand requests that the system deliver the selected program.

The foregoing “on demand’ model of content delivery has placed twosignificant requirements on the delivery system. First, there typicallyis a direct connection between each content storage device (server) andeach listener (client). The phone system is, an example of such apoint-to-point interconnection system. Another example of such aninterconnection system is the Internet, which is also largely based onthe terrestrial telecommunications networks. Second, the servertypically seeks to provide the capability of delivering all the programsto the requesting clients at the time that the client demands theprogramming.

The foregoing requirements can be achieved with limited success,particularly in conjunction with the Internet. The Internet is notsuitable for many types of high bandwidth or on-demand systems. Intoday's Internet, Internet users most often share a terrestrial orperhaps even extra-terrestrial or wireless communicationsinfrastructure; and as a result the total throughput is limited. Inother words, the Internet is typically a party line shared by a largenumber of users and each subscriber must wait for the line to be freebefore he/she can send data. Since the signal from the server isgenerally a high bandwidth signal including multimedia content, anydegradation of the throughput from the server to the clients results inan annoying disruption of the video and/or audio at the clients.Successful transmission of real-time streaming multimedia content,however, requires sufficient transmission bandwidth between the serverand the client. Since standard IP transmission facilities are a partyline, attempts have been made to impose a quality of service (QOS) intothis dominantly party-line transmission structure. One such QOS featureis the bandwidth reservation protocol called “RSVP.” The RSVP protocolmust be active in each network element along the path from the client tothe server for it to be effective. Until RSVP is fully enabled, QOScannot be guaranteed.

Once RSVP is fully deployed, then the mechanical process of reservingbandwidth will be possible to some degree. Nevertheless, even with RSVP,the problem remains that the Internet infrastructure provides limitedtransmission bandwidth. In this regard, consider the case where the sumof all bandwidth reservations exceeds available transmission bandwidth.To reduce the excessive use of bandwidth reservation, transmissionproviders anticipate transmission charges based on the amount ofbandwidth reserved. This bandwidth charge is not in the spirit oftoday's free connectivity.

Another example of the limitations inherent in the finite throughput ofthe Internet is the generally limited audience size for a giventransmission link. For example, if there is a 622 megabit/second (mbs)link from an Internet server in New York to a number of clients in LosAngeles and each client requires a separate 28.8 kilobit/sec (kbs)connection to the server, then this link can only support about 22,000clients, a relatively small number of clients when compared to the costof a server capable of supplying the 622 mbs data content. The costsfurther escalate and the client audience size capability furtherdiminishes as each client connects to the server using higher bandwidthmodems or the like. Still further, the same large demand is placed onthe server if each of the 22,000 clients requests the same program butat different times or if each of the clients request a different programat the same, or nearly the same time. The large bandwidth requirements(622 mbs) to supply a relatively small number of clients (22,000)coupled with the stringent requirements placed on the server to supplythe content to each client has created problems that “on-demand” systemshave yet to economically overcome.

One prior art development in the LAN/WAN technology is called“multicasting.” Multicasting in LAN/WAN parlance means that only onecopy of a signal is used until the last possible moment. For example, ifa server in New York wants to deliver the same data to someone in KansasCity, Dallas, San Francisco, and Los Angeles, then only one signal needsto be sent to Kansas City. There it would be replicated and sentseparately to San Francisco, Los Angeles, and Dallas. Thus thetransmission costs and bandwidth used by the transmission would beminimized and the server in New York would only have to send one copy ofthe signal to Kansas City. This scenario is illustrated in FIG. 1A.

Multicasting helps to somewhat mitigate the transmission costs but thereare still a great number of cases where it provides little optimization.For example, if there is one person in each city in the US that wants toview the same program generated by the server in New York, then theserver must send the signal to all those cities, effectively multiplyingthe amount of bandwidth used on the network. As such, the transmissionis still expensive. Further, the multicast system model breaks down athigh bandwidths and during periods of low data throughput within theInternet infrastructure, resulting in annoying degradation of thetransmission content.

Another issue is distribution of information between autonomous systems.This is called peering. FIG. 1B shows three autonomous simple systemslabeled AS0, AS1 and AS2. These autonomous systems are self containednetworks consisting of host computers (clients and servers)interconnected by transmission facilities. Each autonomous system isconnected to other autonomous systems by peering links. These are shownin FIG. 1B by the transmission facilities labeled PL01, PL02 and PL12.

Peering allows a host in one autonomous system to communicate with ahost in a different autonomous system. This requires that the routers atthe end of the peering links know how to route traffic from one systemto the other. Special routing protocols, such as boundary gatewayprotocol, enable the interconnection of autonomous systems.

Assume that host H1 in AS0 wants to communicate with host H2 in AS1 andH3 in AS2. To do this, H1 communicates with PL01 to reach H2 and PL02 toreach H3. If host Hi wants to multicast a message to multiple hosts ineach of the autonomous systems, then boundary routers involved mustunderstand the multicast protocols.

Backbone providers that form each of autonomous systems are reluctant toenable multicast over their peering links because of the unknown loadplaced on boundary routers and billing issues related to this newtraffic which originates outside of their autonomous systems.

The present inventors have recognized that a different approach must betaken to provide a large amount of content to a large number oflisteners. In their prior art published European patent application, thepresent inventors proposed a system that abandons the “on-demand” modeland point-to-point connection models. In their place, the presentinventors combined, among other things, a particular, unique “broadcast”model with localized multicast connections that selectively allow aclient to receive the high bandwidth content of the broadcast.

As the present inventors' prior published patent application explained,the broadcast model assumes that the server delivers specific content atspecific times on a specific channel as is currently done in today'sradio and television industry. “Near on demand” can be affected byplaying the same content at staggered times on different transmissionchannels, preferably, dedicated satellite broadcast channels. Localizedreceivers receive the broadcast channels and convey the content over anetwork using a multicast protocol that allows any client on the networkto selectively access the broadcast content from the single broadcast.This single broadcast provides, in effect, an overlay network thatbypasses congestion and other problems in the existing Internetinfrastructure.

As also explained in the prior published application: FIG. 1C shows howhost H1 multicast directly to H2 and H3 via satellite or anotherdedicated link separate from the backbone of the Internet. This type ofinterconnection bypasses the peering links and the resulting congestionand billing issues. This type of prior art interconnection maintains,however, a party-line sharing of bandwidth in the dedicated link. Italso is, in essence, generally part of a two-way connection adapted toprovided TCP/IP information exchange in cooperation with, typically, aterrestrial back channel from the satellite reception entity to theentity providing the content for transmission through the satellite orother dedicated link.

The applicants' prior published European application was therefore basedon the applicant's discovery of, among other things, the advantage ofusing a separate dedicated link and implements the resulting solution ina unique manner. Accordingly, the present applicants provided a datatransmission system capable of sending multiple channels of broadcast ormulticasting data or “content” to receiving computers without beingdelayed or impaired by the bandwidth and constraints of two-way Internetconnections.

The applicants' have discovered, however, that one problem with theapplicants system is that, although the near-on-demand delivery is veryadvantageous, by itself, it does not allow for the level of flexibilityan Internet user may desire in playing or accessing content on demandand, for example, long after the near-on-demand delivery has terminatedfor any given content.

Another problem that the applicants have discovered is that thebroadcast model itself is unduly limited in its ability to meet thedemands, and satisfy the needs of, providers of localized orregionalized advertising and similar types of localized content. Thesatellite broadcast model, for example, typically delivers the samecontent to all users nationally. This creates a significant problem fordistribution of localized content, such as locally tailored advertising,through such a non-localized broadcast system. The providers of suchlocally tailored advertising frequently do not purchase advertising insuch non-localized broadcasts, and the potential market demand foradvertising through such mediums is correspondingly limited.

Similarly, those who seek to provide locally-tailored advertising havehad to seek other avenues (such as dealing individually with localizedbroadcasters in each localized market) in order to advertise. Thiseffort is time consuming and expensive.

Also, even when pursuing locally-tailored advertising, advertisers areoften forced by the available traditional media to purchase advertisingin unnecessarily large regions or for delivery to recipients who are notas targeted as might be desired by the advertiser. The applicants'embodiment disclosed in the applicants' prior art patent application didnot solve this type of problem in and of itself.

SUMMARY OF THE INVENTION

The applicants have developed methods and apparatus for multicasting orbroadcasting digital data to users accessing an Internet connection. Themethods and apparatus preferably include placing digital data that is tobe multicast in IP protocol to generate IP digital data. The IP digitaldata preferably is transmitted from a transmission site to a remoteInternet point of presence through a dedicated transmission channelsubstantially separate from the Internet backbone. The dedicatedtransmission channel may be, for example, a satellite channel. At theremote Internet point of presence, local commercials preferably can beinserted into the IP digital data and/or the signal can be delayed forlater playback. The IP digital data is then preferably multicast fordelivery to a receiving Internet users apparatus connected to but distalfrom the remote Internet point of presence.

As will be readily recognized, the foregoing method and apparatuseliminate, or reduce the severity of, problems discussed above inconnection with existing multicast or broadcasting systems. Further,since the principal equipment used to implement the method is disposedat the point of the Internet Service Provider, the normal psychologicalreluctance of an Internet user to purchase extraneous multicastequipment is avoided. Other significant advantages of the applicants'disclosed apparatus and method will become apparent.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are drawings used to illustrate problems in inter-city,communications over, for example, the Internet using conventionalsystems.

FIG. 1C illustrates an alternative delivery system to the system of FIG.1B.

FIG. 1D illustrates a conventional network architecture.

FIG. 2 illustrates a hybrid broadcast I multicast network constructed inaccordance with one embodiment of the present invention.

FIG. 3 illustrates one manner in which the Internet Protocol addressesmay be mapped at an Internet Service Provider.

FIG. 4 is a block diagram of one embodiment of a file server station,such as one suitable for use in the conventional system of FIG. 1.

FIG. 5 illustrates one embodiment of a routine station constructed inaccordance with one embodiment of the present invention and itsconnection within a network domain.

FIGS. 6 and 7 illustrate use of a routing station constructed inaccordance lip the invention and its connection at an Internet ServiceProvider.

FIG. 8 a illustrates one embodiment of an uplink site suitable for usein the network of FIG. 2.

FIG. 8 b illustrates one embodiment of a downlink site suitable for usein the network of FIG. 2.

FIGS. 9-11 illustrate various embodiments of downlink sites suitable foruse in the network of FIG. 2.

FIGS. 12 and 13 illustrate various manners in which various componentsof a downlink site may be modularized and interconnected.

FIG. 14 illustrates one embodiment of the multicast system at an ISPwith distributed POPs that are interconnected with one another.

FIGS. 15 and 16 illustrate one embodiment of an IPMS.

FIG. 17 illustrates a packet protocol that may be used by the controllerunit to communicate through the monitor and control interface software.

FIG. 18 illustrates one embodiment of a transponder unit.

FIG. 19 is a schematic block diagram of selected components of oneembodiment of a transponder unit including a descrambler.

FIG. 20 illustrates one embodiment of a packet filter used in thetransponder unit of FIG. 18.

FIGS. 21-26 illustrate various configurations for networks using an IPMSconstructed in accordance with the present invention.

FIGS. 27-29 illustrate a further manner of deploying the present systemat an ISP.

FIG. 30 illustrates one example of a web page layout for use inselecting baud rate of a video transmission at a user of the presentsystem.

DETAILED DESCRIPTION OF THE INVENTION

The current networking architecture of today is generally illustrated inFIG. 1D. As illustrated, the network, shown generally at 50, comprises agroup of host computers H1-H6 that are interconnected by transmissionlinks P1-P13 and routers R1-R6 to form a LAN/WAN. An aggregated group ofhosts is called a domain. Domains are grouped into autonomous systemsthat are, in-turn, interconnected together to form a network. When thesenetworks span a large geographic area, they are called a wide areanetwork or WAN. An example of this network architecture is the Internetand is illustrated in FIG. 1D.

At each interconnection node is a device called a router, designatedhere as R1-R6. The function of the router is to receive an input packetof information, examine its source and destination address, anddetermine the optimal output port for the message. These receive, routedeterminations, and transmit functions are central to all routers.

If host H1 wants to send a message to host H3, there are a variety ofpaths that the signal could take. For example, the signal could betransmitted along the transmission path formed by P1-P4-P8-P10. Otheralternatives include the paths formed by P1-P2-P5-P7-P9-P10 orP1-P4-P6-P7-P9-P10. The function of the router is to determine the nextpath to take based on the source and destination address. The routermight use factors such as data link speed or cost per bit to determinethe best path for the message to follow.

As more host computers are brought on-line, more domains are created.Each time a domain is created, any router associated with the domainmust announce to its peers that it is present and ready to accepttraffic. Conversely if a domain is deleted, the system must respond byremoving the paths and rerouting all messages around the removed domain.In any large network there will be a constant addition and removal ofdomains. The success of the network architecture to respond to thesechanges is at the core of the networking problem. To this end, eachrouter communicates with its peers to announce to the network ornetworks it services. This implies that a bi-directional link shouldexist at each router. Terrestrial telephone circuits have traditionallysupplied these links on the Internet.

FIG. 2 illustrates a hybrid broadcast/multicast constructed inaccordance with one embodiment of the present invention. The system isillustrated in the context of a plurality of interconnected Internetdomains A, B, and C. As noted above, a domain is an aggregate of one ormore hosts. For example, domain A may be a corporate LAN while domain Bmay be a LAN at an educational institution or the like. In theillustrated embodiment, domain C is shown as an Internet ServiceProvider (ISP) that usually sells local access to the Internet throughits domain. As such, domain C includes at least one access router R7having one or more modems through which local but remotely located ISPcustomers (hosts) 60 connect to the domain through POTS, T1 lines, orother terrestrial links. From domain C, the ISP customers 60 areconnected to the Internet.

In the preferred embodiment, a file server station 100 is used to storeand transmit broadcast transmissions to a satellite 55. As will be setforth in further detail below, the file server station 100 includes oneor more file servers that can provide, for example, multimedia contentin TCP/IP format. The multimedia data is then encapsulated in HDLC orsimilar frame format and modulated to RF for transmission over one ormore uplink channels of the satellite 55. The satellite 55 re-transmitsthe HDSL encapsulated frames on one or more downlink channels havingdifferent carrier frequencies than the uplink channels. The downlinktransmissions are concurrently received by domains A, B, and C at localroutine stations x1, x2, x3. At each routing station x1, x2, x3, theoriginal TCP/IP data transmitted from the file server station 100 isextracted from the received HDLC frames. The extracted TCP/IP data isselectively supplied to hosts within the domain that have made a requestto receive the data.

This satellite 55 network in effect provides an overlay network thatbypasses or at least somewhat avoids congestion and limitations in atleast some of the existing Internet infrastructure, such as in FIG. 1.Moreover, this satellite 55 network provides dedicated, guaranteedbandwidth for the transmission of multimedia data through the satellite55.

In the preferred embodiment, the transmissions from the file serverstation 100 preferably include one or more multimedia transmissionsformatted in accordance with the IP multicast protocol. IP Multicast isan extension to the standard IP network-level protocol. RFC 1112, HostExtensions for IP Multicasting, authored by Steve Deering in 1989,describes IP Multicasting as: “the transmission of an IP datagram to a‘host group’, a set of zero or more hosts identified by a single IPdestination address. A multicast datagram is delivered to all members ofits destination host group with the same ‘best-efforts’ reliability asregular unicast IP datagrams. The membership of a host group is dynamic;that is, hosts may join and leave groups at any time. There is norestriction on the location or number of members in a host group. A hostmay be a member of more than one group at a time.” In addition, at theapplication level, a single group address may have multiple data streamson different port numbers, on different sockets, in one or moreapplications.

IP Multicast uses Class D Internet Protocol addresses, those with 1110as their high-order four bits, to specify groups of IPMS units 120. InInternet standard “dotted decimal” notation, host group addresses rangefrom 224.0.0.0 to 239.255.255.255. Two types of group addresses aresupported: permanent and temporary. Examples of permanent addresses, asassigned by the Internet Assigned Numbers Authority (LANA), are224.0.0.1, the “all-hosts group” used to address all IP IPMS units 120on the directly connected network, and 224.0.0.2, which addresses allrouters on a LAN. The range of addresses between 224.0.0.0 and224.0.0.255 is reserved for routing protocols and other low-leveltopoloyy discovery or maintenance protocols. Other addresses and rangeshave been reserved for applications such as 224.0.13.000 to 224.0.13.255for Net News (a text based service). These reserved IP Multicastaddresses are listed in RFC 1700, “Assigned Numbers.” Preferably,transmissions from the file server 100 containing related multimediacontent are transmitted using a permanent address. Even more preferably,the same multimedia content is provided by the file server system 100 atmultiple data rates using different permanent addresses.

For example, a multimedia file containing an automobile commercial maybe concurrently transmitted for reception at a 28.8 KB data rate, a T1data rate, an ADSL data rate, etc. The 28.8 KB transmission istransmitted using a first group of one or more permanent addresses. TheT1 data rate transmission is transmitted using a second group of one ormore permanent addresses, wherein the first group differs from thesecond group. In this manner, a client having a high speed Internetconnection may chose to receive the more desirable high data ratetransmissions while a client having a lower speed Internet connection isnot precluded from viewing the content due to the availability of thelower speed data transmissions. Additionally, a corresponding web pagemay be concurrently transmitted along with the multicast data or alongthe backbone of the Internet.

If permanent multicast addresses are not available, the TCP/IP addressesused for the broadcast transmissions may use a block of addresses thatare normally designated as administratively scoped addresses.Administratively scoped addresses are used for the transmission ofcommands and/or data within the confines of a domain for administrativeprocesses and are not supplied outside of the scope of the domain. Inother words, any broadcast transmissions received using theseadministratively scoped addresses desirably remains Within the bounds ofthe domain in which it is received. All addresses of the form 239.x.y.zare assumed to be administratively scoped. If administratively scopedaddresses are used, provisions must be made to ensure that the domaindoes not use an administratively scoped address that is within thedesignated broadcast block for other system functions. This may beaccomplished in one of at least two different manners. First, the domaincan be reprogrammed to move the administratively scoped address used forthe other system function to an administratively scoped address thatdoes not lie within the broadcast block. Second, the routing station mayperform an address translation for any administratively scoped addresseswithin the broadcast block that conflict with an administratively scopedaddress used for other purpose by the domain. This translation wouldplace the originally conflicting address outside the conflict range butstill maintain the address within the range of permissibleadministratively scoped addresses. As above, the same multimedia contentis transmitted concurrently using different transmission data rates.

With respect to the use of administratively scoped addresses, assumethat the system will utilize a block of addresses that contain 65,535addresses (16 bits of address space). This block will utilize apredetermined, default address block. For the sake of this description,assume that the system default address space is defined as 239.117.0.0to 239.117.255.255. This address space is defined by fixing the uppertwo bytes of the address space (in this case 239.117) while merelyvarying the lower two bytes of data to allocate or change the address ofa channel of TCP/IP multimedia data. This addressing scheme, in and ofitself, will provide the system with 64K possible channels but it mayplace restrictions on the ISP environment since they would be requiredto have a dedicated block of 64K address space, one in which none of the64K addresses are being used by other applications. This may not alwaysbe feasible. In order avoid this kind of limitation, the system may onlyactually utilize the first 16K of the predefined address space. Thiswill allow 16K channels for the entire system, which corresponds to aminimum aggregate data rate of 470 MHz (assuming every channel isrunning the minimum data rate of 28.8 kbps).

Even with the limited number of addresses, there are still two potentialtypes of problems within the ISP environment. In the first type ofproblem, a limited number of the system broadcast addresses are alreadyin use at the ISP or other domain type. In the second type of potentialproblem, a large block of the system broadcast address space is beingused at the ISP or other domain type. In either case, the IPMS must beable to provide a solution for these two types of problems. These twocases are preferably addressed differently.

The most likely address conflict to be encountered in an ISP is thefirst one noted above, designated here as the “limited address”conflict. This type of conflict occurs when a single address or severalisolated addresses within the broadcast address range are alreadyallocated within the ISP or other domain type. The fact that only 16Kaddresses out of the 64K address block are used will provide a means forroutine “around” these limited address conflicts.

As illustrated in FIG. 3, the 64K address space shown generally at 80will be divided into four 16K address blocks 85. The following diagramshows how the address blocks are defined. The system default addressesare all located in block 0 which begins at address 0 of theadministratively scoped addresses.

The ISP or domain will setup a “routing table” within a routing stationof the domain that indicates all of the administratively scopedaddresses used within the ISP or domain. The routing station isprogrammed to re-route addresses with conflicts to the next availableaddress block. For example, if the ISP has address 239.117.1.11 alreadyassigned, the routing station routes this address to the next availableblock. The next available address block is found by adding 64 to thesecond byte of the IP address. For this service the next address wouldbe 239.117.65.11. If this address is free, this is where the routingstation re-routes the data associated with the conflicting address. Fouralternate addresses may be assigned for rerouting a single channelhaving a conflicting address.

The address re-routing scheme should be implemented on both the routingstation end and in any client Plug-In software used to receive the data.On the routing station side, once the ISP enters all address conflicts,the routing station performs address translation on all of the addressesthat conflicts occur. All packets have their addresses re-mapped to thenew location. If a single address can not be re-routed (all four addressblocks are used for a given channel) then the receiver performs majoraddress block re-routing as would occur in address block conflictmanagement described below. On the client software side, the clientopens sockets for all four address blocks (either sequentially orsimultaneously). The address that provides valid broadcast data isaccepted as the correct channel. The three other sockets are closed. Ifnone of the addresses provide valid data, the client tries the alternateaddress block as defined below.

Alternative strategies for reconciling addressing conflicts may also beemployed. As an example, an agent might be implemented with the IPMSwhich could be queried by the client for the appropriate address to useat a particular location. Such a query would include a “logical” channelnumber associated with the desired broadcast. The agent would thenrespond with the specific IP Address locally employed for thatbroadcast.

If a large number of addresses conflict with the default system addressspace, an alternate block of addresses will be used. The system definesthe exact alternate address space (or spaces), but as an example, if239.117.X.Y is the primary default broadcast block, an address spacelike 239.189.X.Y might be used as an alternate. In any event, therouting station will determine, based on the address conflicts enteredby the ISP, if the entire broadcast address block must be re-routed. Ifit does, the routine station will modify each broadcast channel'saddress. As described above, if the client software can not find a validbroadcast stream within the standard address block, the alternateaddress space will be tried.

Routing multicast traffic is different than the routing of ordinarytraffic on a network. A multicast address identifies a particulartransmission session, rather than a specific physical destination. Anindividual host is able to join an ongoing multicast session by issuinga command that is communicated to a subnet router. This may take placeby issuing a “join” command from, for example, an ISP customer to theISP provider which, in turn, commands its subnet router to route thedesired session content to the host to which the requesting ISP customeris connected. The host may then send the content using, for example, PPPprotocol to the ISP customer.

Since the broadcast transmission is provided over a dedicatedtransmission medium (the satellite in the illustrated embodiment),problems normally associated with unknown traffic volumes over a limitedbandwidth transmission medium are eliminated. Additionally, the numberof point-to-point connections necessary to reach a large audience isreduced since the system uses localized connections within or to thedomain to allow clients to join and receive the broadcast. In theillustrated embodiment, a virtually unlimited number of domains mayreceive the broadcast and supply the broadcast to their respectiveclients, additional domains being added with only the cost of therouting station at the domain involved. In most instances, ISPs or thelike need only add a routing station, such as at x1 et seq., and may usetheir existing infrastructure for receiving broadcasts from the routingstation for transmission to joined clients. This is due to the fact thatmost ISPs and the like are already multicast enabled using the IPmulticast protocol.

FIG. 4 illustrates a block diagram of one embodiment of a file serverstation, such as the one illustrated at 100 of FIG. 1. The file serverstation, shown generally at 100, comprises a local area network 102 witha collection of server PCs 105 connected to a router 110 over the localarea network 102. The server PCs 105 include server software that eitherreads pre-compressed files from the local disk drive and/or performsreal time compression of analog real time data. Each server 105 providesthis data as output over the local area network.

The LAN 102 performs the function of multiplexing all the streaming datafrom the server PCs 105. The LAN 102 should have sufficient bandwidth tohandle all the data from the server PCs 105. In present practice, 100mbs LANs are common and. thus, it is quite feasible to use 100 mbs LANsto aggregate the data output to a 30 mbs transponder. A common type ofLAN is or 100Base T, referring to 100 mbs over twisted pair wire.

The functionality required at 110 is to gather the packets of data fromthe LAN 102, wrap them in a transport protocol such as HDLC, and convertthe HDLC packets to the proper voltage levels (such as R5422). Thefunctionality can be provided by the composite signal provided from therouter 110 usually comprises clock and data signals. The compositesignals are output from the router 110 for synchronous modulation by asatellite uplink modulator 115 which synchronously modulates the data tothe proper RF carrier frequencies and transmits the resulting signalthrough an antenna 122 to the satellite 55.

One or more server PCs 105 of the LAN 102 store the multimedia contentthat is to be broadcast to the domains. Alternatively, the one or morePCs 105 may receive pre-recorded or live analog video or audio sourcesignals and provide the necessary analog-to-digital conversion,compression, and TCP/IP packet forming for output onto the LAN wanted.These packets are transported over the LAN 102 in an asynchronousmanner. The router 110 then receives these asynchronous packets andencapsulates them with the transport protocol and transmits them in asynchronous manner to the satellite 55. The constant conversion from oneform to another is provided to fit the transmission technologies of thetransmission equipment. LANs are becoming ubiquitous and low cost sinceit leverages the high manufacturing volumes of the consumer/corporate PCmarket. Satellite transmission is extremely cost effective forbroadcasting signals to multiple destinations and is inherentlysynchronous (data is transmitted at precise intervals). Accordingly, theforegoing system is currently the most straight forward and lowest costmethod to architect a system a connecting computer LANs to a satellitetransmission system.

A typical satellite 55 has two antennas, one for receiving the signalfrom the uplink and the second antenna for transmitting the signal tothe downlink. An amplifier is disposed between the two antennas. Thisamplifier is responsible for boosting the level of the signal receivedfrom the file server station 100 (uplink). The received signal is veryweak because of the distance between the uplink and the satellite(typically about 23,000 miles). The received signal is amplified andsent to the second antenna. The signal from the second antenna travelsback to downlinks which are again about 23,000 miles away. In theillustrated embodiment of the system, the downlinks are the routingstations.

The signal is transmitted by the uplink at one frequency and shifted toa different frequency in the satellite before amplification. Thus, thesignal received by the satellite is different from the frequency of thesignal transmitted. The transmitted information content is identical tothe received information.

A typical satellite has approximately 20 to 30 RF amplifiers, each tunedto a different frequency. Each of these receive/transmit frequencysubsystems is called a transponder. The bandwidth of each of thetransponders is typically about 30 MHz but can vary satellite tosatellite.

At the file server station 100, the composite signal from the router 110is preferably QPSK modulated by the satellite uplink modulator. Duringthe modulation process, extra bits are usually added to the originalsignal. These extra bits are used by a receiver at the downlink tocorrect any errors which might occur during the 46,000 miletransmission. The extra protection bits that are a added to the datastream are called Forward Error Correction bits (FEC).

The resulting modulation and error correction process typically allowsabout 1 megabit/second of data to occupy about 1 megahertz (MHz) ofbandwidth on the transponder. Thus, on a 30 MHz bandwidth transponder,one can transmit about 30 mbs of data. The aggregate data rate of thesignals generated by all server PCs 105, including the overhead of theunderlying transmission protocols (IP and HDLC), must be less that thebandwidth of the satellite transponder.

FIG. 5 illustrates one embodiment of a routing station and itsconnection within a domain. Here, the routing station is called an IPMulticast Switch (IPMS), labeled as 120 in FIG. 5. The IPMS 120 iscomprised of a demodulator 125 that receives the radio frequency signalsfrom the satellite 55 over receive antenna 130 and converts them intothe original TCP/IP digital data stream. These digital signals are theninput to a device called a IP Multicast Filter (IPMF) 140 that in-turnselectively provides the signals as output onto a LAN, shown generallyat 145, having sufficient capacity to handle all the received signals.The IPMS 120 is multicast enabled, meaning that data is only output fromthe IPMF 140 onto the LAN 145 if a client 160 requests a connection toreceive a broadcast channel. As noted above; this multicast protocol maybe one such as defined in RFC 1112.

As illustrated, the LAN 145 can be connected to the Internet 165 througha router 170. If the broadcast data output on the LAN 145 usesadministratively scoped addresses, the router 170 can prevent forwardingof the data to the Internet 165. This is a desirable feature associatedwith the use of administratively scoped addresses, as the broadcast canbe localized and blocked from congesting the Internet 165. If otheraddresses are used, such as permanent IP multicast addresses, the router170 is programmed to prevent data having an IP multicast address frombeing broadcast on the Internet 165.

The software of the IPMS 120 is capable of operating in an IP multicastnetwork. In the embodiment described here, the control structure of themulticast software in the IPMS 120 has four main threads:initialization, multicast packet handling, LAN packet handling, andmulticast client monitoring. In the initialization thread, a table usedto determine whether a client has joined a broadcast has its content setto an empty state. Initialization is performed before any of the otherthreads are executed.

The multicast packet handling thread is responsible for reading datafrom the satellite demodulator and deciding what is to be done with it.To this end, the thread reads each multicast packet received from thesatellite demodulator 125. If the multicast group address specified inthe received packet is not in a group table designating the groupsreceived from the satellite 55 by the demodulator 125, the group addressis added to the group table and set to “not joined.” If the multicastgroup address specified in the packet is specified in the join table ashaving been joined by a client, the packet is output through the IPMS120 to the LAN 145 for receipt by a requesting client 160. If none ofthe foregoing tests are applicable, the packet is simply ignored.

The LAN packet handling thread is used to determine whether a joincommand has been received from a client 160 over the LAN 145. To thisend, the IPMS 120 reads an IP packet from the LAN 145. If the packet isa request from a client 160 to join the multicast session and it is in agroup table (a table identifying groups which the IPMS 120 is authorizedto receive), the group address is added to the list of joined addressesin the join table. In all other circumstances, the packet may beignored.

The multicast client monitoring thread is responsible for performingperiodic checking to ensure that a multicast client who has joined abroadcast is still present on the LAN 145. In accordance with RFC 1121,every predetermined number of seconds, or portions thereof, for eachgroup address in the group table which has joined the multicast sessiona query is sent to that address and the IPMS 120 waits for a response.If there is no response, the IPMS 120 assumes that all joined clientshave terminated and removes the group address from the joined list.

It will be recognized that other further software threads and variationson the foregoing threads may be used. However, in the simplest form ofthe illustrated embodiment, the four threads described above are allthat is practically needed for effective IPMS operation where the IPMS120 is disposed at an outer edge of a domain network. Thissimplification provides a reduction in complexity in the IPMS 120.

If there are one or more routers between the IPMS 120 and the multicastclient 160, then the IPMS 120 is programmed to understand the variousmulticast protocols such as DVMRP, MOSPF and RIM. These protocols arewell known and can easily be implemented in the IPMS 120.

In either configuration, the IPMS 120 appears to the domain network asthe source of the data, and the satellite link effectively places anidentical server at each downlink location in the separate domainsdescribed in connection with FIG. 2.

It is generally preferable to have the IPMS 120 as close as possible tothe last point in the network before transmission to a client. Thisclose proximity to the client minimizes the traffic burden on othersystem routers and the overall local LAN. The Internet ServiceProvider's (ISP) local Point of Presence (POP) is generally the optimumlocation for placement of the IPMS 120 at an ISP. Such a configurationis illustrated in FIG. 6.

As shown in FIG. 6, the ISP, shown generally at 200, is connected via anaccess router 205 to the Internet 165. If a distribution router 210 islocated some distance from the Internet access router 205, theninter-POP communications are required through one or more intermediaterouters 207. These inter-POP communications may take place via framerelay or SMDS (Switched Multimegabit Data Service) since these arerelatively inexpensive communication methods. In the POP 215, the IPMS120 is connected to the backbone LAN 220. This LAN 220 is connected tothe distribution router 210 and provides the connectivity to thecustomer base. Typically, the distribution router 210 is connected to aLocal Exchange Carrier (LEC) 230 through telephone company interconnectssuch as T1, T3, and ATM lines and, thereafter, to remotely located homeusers/clients 235.

The architecture of FIG. 6 allows customers 235 to place local (free)calls into the distribution router 210 that, in turn, allows thecustomers 235 to access the Internet 165 through some remote accesspoint. If the POP 215 and the Internet access at access router 205 areco-located, then the ISP LAN 240 and the POP Backbone LAN 220 are one inthe same and there are no intermediate routers or intervening inter-POPcommunications.

FIG. 7 illustrates a system in which the IPMS 120 is not disposed at thePOP 215 location. This arrangement is functional, but requires a largeamount of bandwidth over the inter-POP communication lines 245. Theconfiguration shown in FIG. 6 minimizes the bandwidth requirements ofthe router interconnections relative to the configuration shown in FIG.7 since only the POP Backbone IAN should include both the traditionalInternet traffic as well as the Multicast traffic.

As can be seen from examination of FIGS. 6 and 7, the addition ofmulticast equipment to the ISP's POP 215 is minimal. It is also possibleand desirable to add a traffic server PC 255 onto the LAN of the ISP 200having the IPMF 120 (also known as a multicast switch). This trafficserver 255 can be used for a varies of purposes, but in the embodimentshown here, it is used to store information received from the satellite55 and the Internet 165 for later playback. It also can be used tomonitor the number and identification of a connected user as well asperforming other functions. For example, when a user selects avideo/audio multicast channel to view/hear, it sends a specific IGMPmessage over the LAN that is directed to the IPMS 120. This message canalso be monitored by all systems connected to the LAN. Specifically, thetraffic server 255 may monitor the communication between the router 210and any connected clients and may also monitor the number of connectionsto the multicast channels. The connection information gathered by thetraffic server 255 is preferably relayed to a central server or the likeover the Internet 165 at periodic intervals for consolidation at acentral facility.

One advantage of the foregoing system architecture is that it provides ascaleable architecture that may be scaled to deliver a small number ofmegabits as well as further scaled to deliver nearly a gigabit ofcontent to a large number of host computers. This architecture is onlyconstrained by satellite transponder capacity, which is typically about30 mbs per transponder.

FIGS. 8 a and 8 b illustrate the uplink and downlink systems suitablefor handling at least 60 mbs. File server stations, such as the oneshown at FIG. 4, typically only have a capacity of 30 mbs. As such, theuplink here uses two file server stations 100 a and 100 b. On the uplinkside, a second cluster of server PCs 105 is connected to a second router110 b, which is connected to the uplink equipment and transmits thesignal over the same satellite 55 using a different transponderfrequency. Alternatively, the transmission of signals from the secondrouter 110 b may be directed to a different satellite than the one usedby the first file server station 100 a. If the two signals are uplinkedonto the same satellite, then it is possible to share a common antenna.

At the downlink side of FIG. 8 b, there are two IPMS units 120 a and 120b, which are each identical to that described above. If the two signalsare uplinked on the same satellite, it is possible to share an antenna130 on the downlink as shown in FIG. 8 b. If not, then two separateantennas are required, one pointing to each of the different satellites.In the scenario shown in 8 b, the two IPMSs 120 a and 120 b areconnected to a 100baseT LAN 280. The maximum bit-rate delivered to theLAN 280 is the sum of the individual bit rates of the IPMSs 120 a and120 b, or about 60 mbs. This is a convenient number since the maximumreal capacity of a 100BaseT LAN is about 60 mbs.

Additional file server stations and IPMSs may be added to the foregoingsystem to increase the number of available multimedia multicast channelsavailable to the ISP clients. For example, a 90 mbs system may beconstructed by adding a further file server station at the uplink sideof the system and adding a further IPMS at the ISP POP. This third IPMS,however, presents a problem for a 100BaseT LAN since the total possiblethroughput can now exceed the allowable LAN bandwidth. The trafficserver 255 can be used to assist in eliminating this problem.

At the heart of the multicasting protocol is the fact that generally nounnecessary traffic is forwarded unless someone has requested it. Thismeans that even if there is 90 mbs of total data received from thesatellite, there would be no data output to the 100BaseT LAN if therewere no clients requesting a connection to it.

On the other hand, it is possible that there could be clients requestingplacement of the entire 90 mbs on the LAN. Such traffic would saturatethe LAN 280. To mitigate the problem, there are at least two potentialsolutions.

The first solution is to modify the client software so that it firstcontacts the traffic server 255 to determine how much bandwidth isalready delivered to the LAN 280. If the LAN is already delivering themaximum possible data to other clients, then the client currently tryingto connect is given a message stating that the system is too busy.

A second solution is to have an IPMS first contact the traffic server255 to check the load on the LAN 280 before providing a channel ofmulticast data on the LAN 280. To this end, the IPMS 120 contacts thetraffic server 255 after a request has been made for a channel ofmulticast data but before the data is supplied on the LAN 280. If thetraffic server 255 deems that the load is too high, it instructs theIPMS 120 to ignore the join request and refrain from transmitting therequested group on the LAN 280. As a result, the requesting client wouldnot receive the requested video/audio stream. The client software mayindicate the failure to receive the requested data upon termination of apredetermined time period and indicate this fact to the user.Nevertheless, the applicants believe that there is a high probabilitythat 90 to 120 mbs of data could be uplinked with no downlink overloadon the LAN, since it is highly unlikely that all data rates of allchannels would be simultaneously used.

The traffic server software could be imbedded into one of the IPMulticast Switches 120 and thus eliminate separate traffic serverhardware 255. If the system data is scaled even higher, then thearchitecture shown in FIG. 9 is used at the downlink side of the system.The transmission data rate at the uplink side is obtained by merelyadding further file server stations 100. The system shown a in FIG. 9adds a new piece of hardware called gigabit switch 290. On the rightside of the switch 290 is a connection to the LAN 300. The LAN 300 inthis embodiment is capable of handling the total aggregate bandwidthoutput by all IPMSs 120. For the case where each IPMS 120 is receiving30 mbs and there are 10 IPMSs, then the aggregate bandwidth is 300 mbs.This implies that the LAN 300 is capable of handling such traffic.

As further illustrated in FIG. 9, a controller 310 may be used tocommunicate with the LAN 300 and, further, with the demodulators 125 andIPMFs 140 over a communication bus 315. Such an architecture allows thecontroller 310 to program the specific operational parameters used bythe demodulators and IPMFs. Additionally, the demodulators 125 and IPMFs140 may communicate information such as errors. status, etc., to thecontroller 310 for subsequent use by the controller 310 and/or operatorof the routing station. Still further, the traffic server 255 may beused to facilitate inter-module communications between the IPMFs 140.

The connections between the IPMF 140 and the switch 290 may be the100BaseT connections shown in the previous figures. This implies thatthe switch 290 requires n-100BaseT input ports to accommodate the n-IPMSinputs. The system proposed in FIG. 9 assumes the use of gigabit accessand distribution routers, gigabit LANs and gigabit switches. Suchnetwork components are in the very early stages of deployment.

A second architecture that can be used to scale to a large number of ausers is shown in FIG. 10 and is similar to the architecture shown inFIG. 9 in that then both include the satellite demodulators 125 and theIP Multicast Filters 140. The system of FIG. 10, however, replaces thetraffic server 255 with an IP filter 325 and the gigabit switch 290 witha standard 100BaseT hub 340. Another significant difference between thetwo architectures is that the Internet access router 205 of FIG. 10 isdirectly connected to the backbone of the gigabit LAN while theconnection for the Internet access by the clients 335 is through the IPfilter 325 within the LAN interface module. The IP filter 325 may beimplemented by a PC or the like, or by a microcontroller, The IP filter325 performs the functions of the traffic server 255 as well as simpleIP packet filtering. It passes each packet received from the Internetwithout examination or modification. This includes multicast as well asunicast traffic. Packets received from the hub 340 are examined on a perpacket basis. Multicast packets with a group address used by thesatellite delivered multicast system (shown here as the SatelliteInterface Unit (SIU)) are blocked from traversing onto the Internet.This prevents the Internet Access LAN from overload and serves thefunction of administratively scoping the multicast traffic to onesegment. This architecture also has an added advantage in that therouters used in the domain do not have to be multicast enabled.

The architecture shown in FIG. 10 can be viewed as dividing an ISP intosmaller ISP's within the larger ISP. Each of these mini-ISPs has its ownIAN Interface Unit (LIU) 405. This architecture places a performancerequirement on the IP filter in that it must be capable of processingall packets flowing through it via the 100BaseT LANS to which it isconnected.

FIG. 11 illustrates a further system architecture that replaces the IPfilter 325 of FIG. 10 with a traffic server 255 and uses a 10/100 BaseTswitch 410 in place of the IP filter 325. This architecture requires the10/100 BaseT switch 410 to perform the IP multicast filtering that wasdone in the IP filter 325.

The interface point 417 of FIG. 11 between the IPMS and a particular ISPLAN segment, may also be facilitated in cases where that LAN segment isremotely located. Standard digital telecommunications services may beemployed to serve as electrical “extension cords” to bring the output ofthe IPMS onto the remotely located segment. This is done throughcommonly available “CSU/DSUs” that can transform the LAN output of theIPMS into a digital signal compatible with the Network Interfacerequirements of common communications carriers, and at the remotelocation, a subsequent translation back into the required 100BT LANsignal.

FIG. 12 shows one manner of implementing the architectures for thesatellite downlink. The IP Multicast Switch 120 can be functionally andphysically divided into a satellite interface unit 425 and a LANinterface unit 430. Multiple LAN interface units 430 may be connected toa single satellite interface unit 425. This allows the satellitereception equipment to be located at a first location and its outputdistributed to various remotely located LAN interface units. As shown inFIG. 3 the basic system architecture of FIG. 12 also allows for thedistribution of content via an alternate transmission facility such asterrestrial fiber 110. Alternatively, these two modules can reside inthe same chassis and use the chassis backplane for intermodulecommunication.

FIG. 14 illustrates an embodiment of the system at an ISP withdistributed POPs that are interconnected with one another. Thisembodiment of the system isolates the multicast traffic from the unicasttraffic. Inter-POP multicast traffic is carried on a separatetransmission facility.

One embodiment of an IPMS discussed earlier is illustrated in FIGS. 15and 16. Generally stated, the embodiment of the IPMS unit 120 shown hereand subsequently described is comprised of a controller unit 440 and oneor more transponder units 445. The controller unit 440 handles themonitoring, control, and configuration of the IPMS unit 120. Thetransponder units 445 performs demodulation and de-packetization of theRF signal data received from the satellite 55 and provides thedemodulated data to the hub 340 of a 100BT LAN 220 when directed to doso by the controller unit 440. In some implementations of the system,there may be a need for a splitter unit 450 that divides the RF signalfor supply to several transponder units 445.

As noted above, the controller unit 440 handles all monitor, control,and configuration of the IPMS unit 120. It maintains logs of all of theevents in the system and processes all incoming TCP/IP protocol messagesto the IPMS unit 120. These messages include the IGMP join requests fromremote clients, individually addressed commands to the controller unit440, and packets destined to individual transponder units 445. Thecontroller unit 440 is responsible for logging all of the trace typeevents in a non-volatile memory device, such as a hard disk drive 455.

As illustrated, the controller unit 440 is comprised of a microprocessorunit 460, two network interface cards (NIC) 465 and 467, a modem 470 forconnection to a remote port, a video controller 475 for connecting avideo monitor, a keyboard interface 480 for connection to a keyboard, aDRAM 485 for storage, an RS-232 port 487 for external communications,and the hard drive 455.

The microprocessor unit 460 may be an Intel Advanced ML (MARL) Pentiummotherboard. This board has two serial ports, a parallel port, a busmastering IDE controller, a keyboard interface, a mouse interface,support for up to 128 MB of DRAM, and a socket for a Pentiummicroprocesser. The board supports 3 ISA extension boards and 4 PCIextension boards. The MARL motherboard is designed to fit into thestandard ATX form factor.

The RS-232 port 487 supports commands from a remote port that can beused for both monitor and control functions. This interface supportsstandard RS-232 electrical levels and can be connected to a standardpersonal computer with a straight through DB-9 cable. The software usedto implement the interface supports a simple ASCII command set as wellas a packet protocol that can be used to send commands that containbinary data.

Monitor and control interface software 490 executed by themicroprocessor unit 460 supports multiple communications settings forthe RS-232 port 487 by allowing the user to change the baud rate, thenumber of data bits, the number of stop bits, and the type of parity.These settings are saved in non-volatile memory so that they arepreserved after power has been removed from the receiver.

The monitor and control interface software 490 preferably supports botha simple ASCII protocol and a more complex packet structure. The ASCIIprotocol is a simple string protocol with commands terminated witheither a carriage return character, a line feed character, or both. Thepacket protocol is more complex and includes a data header and aterminating cyclic redundancy check (CRC) to verify the validity of theentire data packet.

The ASCII protocol is preferably compatible with a simple terminalprogram such as Procomm or HyperTerminal. When an external terminal isconnected to the RS-232 port 47, the controller unit 440 initiallyresponds with a sign-on message and then displays its “ready” promptindicating that the is ready to accept commands through the monitor andcontrol interface software 490. Commands are terminated by typing theENTER key which generates a carriage return, a line feed, or both. Thecontroller unit 440 interprets the carriage return, as the terminationof the command and begins parsing the command.

Most commands support both a query and a configuration form.Configuration commands adhere to the following format:cmd param1<,param2>CRwhere cmd is the command mnemonic, param1 is the first parametersetting, the <,param2> indicates an optional number of parametersseparated by commas, and CR is a carriage return.

Queries of commands can be entered in one of two forms as follows:cmd?CR or optionallycmdCRThe controller unit 440 responds to the query with the command mnemonicfollowed by the command's current setting(s).

The controller unit 440 may also communicate through the monitor andcontrol interface software 490 using a predetermined packet protocol.One such protocol is illustrated in FIG. 17. The illustrated protocol isan asynchronous character based master-slave protocol that allows amaster controller to encapsulate and transmit binary and ASCII data to aslave subsystem. Packets are delimited by a sequence of characters,known as ‘flags,’ which indicate the beginning and end of a packet.Character stuffing is used to ensure that the flag does not appear inthe body of the packet. A 32-bit address field allows this protocol tobe used in point-to-point or in point-to-multipoint applications. A 16bit CRC is included in order to guarantee the validity of each receivedpacket.

The opening flag 500 includes a 7E_(H)01_(H) flag pattern indicating thestart of packet or end of the packet at 510. A transaction ID 505follows the opening flag 500 and is, for example, an 8-bit value thatallows the master external computer to correlate the controller unit 440responses. The master computer sends an arbitrary transaction ID to thecontroller unit 440, and the controller unit 440 preferably respondswith the 1's complement of the value received from the master. Followingthe transaction ID 505 is a value that allows the master to identify theaddressing mode of the packet. This portion of the packet is called themode byte and is shown at 515. These addressing modes include broadcast,physical, and logical modes. An address field 520 and data field 525follow the mode byte 515. The address field value is used in conjunctionwith the mode field to determine if the slave should process the packet.The data field 525 contains information specific to the application.This field can be any size and is only limited by the application.Finally, a CRC-16 field 530 follows the data field 525. The CRC-16 field530 allows each packet to be validated. Each byte from the mode byte 515to the last data byte is included in the CRC calculation.

The monitor and control interface software 490 supports the same commandset as both a remote port and a TCP/IP in-band signaling channel. Thisallows the IPMS 120 to be controlled identically using any of thepossible control channels (although the physical connection and physicalprotocol vary by connection) which provides redundant means of monitorand control. These commands are described in further detail below.

The controller unit 440 includes the hard drive 455 for its long-termstorage. This drive is preferably at least 2.1 GB in size and uses astandard IDE interface. The drive 455 is preferably bootable and storesthe operating system, the application(s) running the IPMS 120, and alllong-term (non-volatile) data such as history/trace data.

The network interface card 465 is used to communicate with all of thetransponder units 445 in the IPMS 120. The network interface card 465 iscomprised of a 10 based-T LAN interface running standard TCP/IP.Individual commands are issued using the same protocol as set forthabove in connection with the monitor and control interface software 490as well as any remote port connected through modem 470. This protocol isencapsulated into TCP/IP and sent via an internal LAN 532 overtransmission line 535.

The network interface card 465 supports both broadcast and individualcard addressing. This interface also supports two-way communication thatcan be initiated by any unit on the internal LAN 532. Individualtransponder units 445 may communicate with each other over the internalLAN 532, although this interface is not truly intended to be used inthis fashion in the embodiment shown here. The 10 Based-T interface card465 may be implement using any off-the-shelf network interface card.

The modem 470 of the controller unit 440 may also support commands thatcan be used for both monitor and control functions. The modem 470supports standard phone modem electrical levels and can be connected toa standard phone jack with a straight through RJ-11 cable. Both theASCII and packet protocols noted above are supported by the modem 470.The modem 470 thus provides another communications route to the IPMS 120in case a standard TCP/IP link over the Internet to the IPMS 120 fails.

The modem interface 470 is implemented for example, by an off-the-shelfmodem and auto-negotiates all communications settings with a NetworkOperations Center or NOC 472 at a location that is remote of the ISP.The Network Operations Center 472 preferably uses an identical modem.

The IPMS 120 includes several miscellaneous input and output (IO)functions that are not illustrated in FIGS. 15 and 16. These functionsmay be handled on either a plug in ISA board or a front panel board. TheIO may include status LEDs, a status dry contact closure, and a panicbutton. The status LEDs may be set through an I/O card. LED indicatorsmay include Power Present, Power OK, Fault, Test, Carrier OK, and LANActivity. The Power Present LED may indicate that the IPMS 120 isplugged into its main AC source. The Valid Power LED may indicate if thepower within the IPMS 120 is within valid tolerance levels. The FaultLED may indicate if a major fault is occurring in the IPMS 120. The TestLED may indicate that the IPMS 120 is in a test mode, either its powerup test or an on-line test mode. The Carrier LED may indicate that alltransponder units 445 that should be acquired (have been programmed tolock onto a carrier) are, in fact, locked. If any single transponderunit 445 is not locked, this LED will be off. The LAN activity LED mayindicate that the IPMS 120 has activity on its 100 based-T LAN.

A Form C dry contact closure may be provided to indicate the status ofthe IPMS 120. If the IPMS 120 goes into a fault condition, the IPMS 120will provide an output signal along one or more lines at 540 to driveclosure to a closed state. This provides a means of monitoring theoverall operational integrity of the IPMS 120 with an external devicetriggered by the contact closure. Devices that could be used includeautomatic pagers or alarm bells.

The IPMS 120 may also have a panic button that is used to turn offoutgoing multicast video. This will provide the ISP with a quick andefficient way of stopping the IPMS 120 data flow onto the ISP LAN 240 incases of extreme LAN congestion or a when a malfunctioning IPMS 120inadvertently congests the LAN 240. This button preferable will not takethe controller unit 440 link off of the network. This ensures that thecontroller unit 440 will still be susceptible to monitoring and controlthrough the TCP/IP port connected to the ISP's LAN 240.

Once the panic button has been pressed, the IPMS 120 issues a “LANshutdown” to every transponder unit 445 through the network interfacecard 465. The individual transponder units 445 are responsible forshutting their LAN output off.

Controller Unit Software Functionality

The following sections provide a brief overview of one embodiment of thesoftware functionality used to operate the controller unit 440. Thissoftware is preferably developed in accordance with an object-oriented,C++, methodology.

The controller unit 440 preferably runs under a Microsoft Windows NTWorkstation operating system. This operating system supports all of thenetworking protocols needed as well as supporting the hardware found inthe controller unit 440.

1. Networking Protocols

The networking protocols discussed above are supported by the operatingsystem. The operating system runs an HTTP server that allows control ofthe controller unit 440 through a web browser type of application.

2. Watchdog Process

A hardware watchdog timer counter that must be periodically reset isused in the controller unit 440. If this counter runs out, it generatesan interrupt that reset as the controller unit 440. In addition to thissystem level watchdog timer, individual applications may maintain theirown versions of watchdog monitoring to ensure that they do not “hang.”In cases where an individual task can restart without affecting theoverall system, the task will be restarted. In cases where the systembecomes unstable, the entire controller unit 440 is preferably restartedin an orderly manner. In either case, an error should be generated andlogged in the trace buffer.

3. Software Download

The controller unit 440 handles software downloads for itself and forall of the transponder units 445: Software downloads are preferablyperformed using FTP file downloads over the local ISP LAN the 240through NIC 467, from a remote station over the modem interface 470, orthrough the RS-232 port 487. Before a file is downloaded, FTP serversoftware in the controller unit 440 verifies that the download is, infact, a new file. The files are preferable downloaded into a fixeddirectory structure.

4. Network Configuration Tables

The NOC 472 maintains a series of tables used to configure a network ofsystems such as the one shown in FIG. 15, each system being linked tothe NOC 472. These tables may be downloaded using FTP or a predeterminedtable download command and are used by the controller unit 440 toconfigure all of the transponder units 445 and to handle any data rateadaptation required by the system. The tables include a ChannelDefinition Table (CDT), a Carrier Table (CT), and a Channel ClusterTable (CC).

The Channel Definition Table (CDT) is used to define the location andbandwidth of every channel containing, for example, multimedia content,in the overall system. Each channel of the disclosed embodiment has aunique ID that ranges from 0 to 16K. This ID is the same value as thechannel's default low order administratively scoped address bits. Forexample, channel 128 will have a default address of X.Y.0.128, where Xand Y are the administratively scoped high order address bytes (239.117for example). The CDT also provides an indication of the carrierfrequency on which a channel can be found. The carriers are assigned aunique ID number that can be converted to a frequency and data rateusing the Carrier Table set forth below. The CDT also includes theChannel Cluster ID of the cluster in which the channel appears, if any.The Channel Cluster ID is defined in the Channel Cluster Table sectionbelow. Each CDT record preferably uses the following record format:

Channel ID (8-bits) Transponder Number (16-bits) Data Rate (inKilobytes) (16-bits) Cluster ID (16-bits)

The CDT only contains records for defined channels in the overallsystem. If a channel is not defined, the IPMS 120 will assume that thechannel has zero bandwidth. The overall table will be represented in thefollowing form:

Table ID (8-bit) Number of Channels (16-bit) Channel Records (40-bitsper record * number of channels) CRC (l6 bit)

The Carrier Table (CT) provides a means for identifying all of thecarriers being used in the overall system. The records in the CTindicate the satellite transponder ID, the frequency of the carrier, itsdata rate, and the type of coding that the carrier is using (includingscrambling). The controller unit 440 provides these parameters to thetransponder units 445 to acquire the desired carrier. The CT recordsalso contain information about the satellite that the carrier istransmitted from and the polarity of the receive signal. The controllerunit 440 uses this information to notify an installer. through, forexample, a video terminal attached to the video controller 475, thatmultiple dishes are required. Further, the satellite ID is used todetermine the azimuth and elevation settings for an antenna that is toreceive the carrier transmission from the identified satellite. Eachrecord within the CT preferably has the following format:

Carrier Number (16-bits) Frequency (in kHz) (32-bits) Data Rate (in Hz)(32-bits) Coding type (8-bits) Polarity (8-bits) Satellite ID (8-bits)The overall table format for the CT is as follows:

Table ID (8-bit) Number of Carriers (16-bit) Carrier Records (104-bitsper record * number of carriers) CRC (16-bit)

The Channel Cluster Table (CCT) is used to describe a “cluster” ofchannels. A cluster of services is defined as a set of multiple channelswith the same content but using different data rates. This aspect of thepresent embodiment of the system is set forth above. The CCT is used toallow a client to receive a channel at a different data rate from theone requested. For example, if a client requests a service at 1 Mb butthe LAN 240 is congested or the controller unit 440 is close to itsmaximum allowable bandwidth on the LAN, the controller unit 440 caninform the client software (usually a browser plug-in or the like) toswitch to another channel in the cluster at a lower data rate, say 500kb. To facilitate lookup times, each channel has its associated clusterID in its record within the Channel Definition Table. This allows thecontroller unit 440 to easily locate a channel ID, determine its ClusterID, and find alternate channels. Each Channel Cluster record preferablyconforms to the followings record format:

Cluster ID (16-bits) Number of Channels in Cluster (8-bits) Service ID'schannels) (16-bits * the number of channels)The overall table format for the CT is as

-   -   Table ID    -   Number of Clusters    -   Cluster Records    -   CRC    -   (16-bits)    -   (8-bits)    -   (16-bits*the number of follows:    -   (8-bit)    -   (16-bit)    -   (24+(16*the number of channels)*numbers of clusters)    -   (16 bit)

5. Networking Protocols

As discussed above, the controller unit 440 may receive Internet relatedprotocol messages. It processes such messages and performs the necessaryactions to maintain the controller unit environment. For example, whenthe controller unit 440 receives an IGMP join message from an end-userclient application requesting a new service, it may respond with apredetermined sequence of action. For example, the controller unit 440logs the join request, verifies that there is enough bandwidth on theLAN 240 to output the service, and sends an Add Service command to theappropriate transponder unit 445. The controller unit 440 then sends aresponse back to the client indicating whether or not the join wassuccessful.

6. Inter-IPMS Communications

The controller unit 440 communicates with the transponder units 445, andany I/O units that are utilized, through the 10 based-T LAN, shown hereat 532. The software of the controller unit 440 maintains a TCP/IPprotocol stack to support this interface.

7. Serial Communications Over the Modem 470 and RS-232 Port 487

The controller unit 440 utilizes the monitor and control software 490described above to handle the modem 470 and RS-232 port 487 serialcommunications ports. The serial ports are used to send commands to andfrom the controller unit 440. The commands supported through thisinterface are the same as the commands through the 100 based-T LANinterface 240.

8. Command Processor

Command processor software tasks handle commands that have come in fromthe various command channels (modem 470, port 487, etc.) supported bythe controller unit 440. The commands are parsed and executed as needed.

9. System Event Logging

All significant events may be logged into a trace buffer in, forexample, the non-volatile memory (hard drive 455). The controller unitsoftware tasks will take an event, timestamp it, and put the resultingstring into a trace buffer. The software routines may disable individualevents from being put into the log and may control the execution of thelogging process (start, stop, reset, etc.).

10. Status Monitoring

A status-monitoring software task in the controller unit 440 monitorsthe current status of the controller unit 440 and periodically pollseach of the transponder units 445 for their status. This task maintainsan image of the current status as well as an image of past faults thathave occurred since the last time a fault history table was cleared (viacommand). This task further reports fault and status information to theNetwork Operations Center 472 over, for example, an Internet connectionor modem 470.

11. Statistics Gathering

The statistics gathering task of the controller unit 440 is similar tothe status monitoring software described above. This process keeps trackof the number of users “viewing” a particular channel, the addresses ofusers, the number of collisions on the LAN 240, and other long termstatistics that may be helpful in monitoring the usage of the IPMS 120.

12. Power Up Sequence

The power up sequence software of the controller unit 440 starts allnecessary start-up tasks, determines if the transponder units 445 needto be programmed, performs all needed power up diagnostic functions, andjoins the in-band signaling group address of at least on transponder.

13. Dish Pointing Calculation

The controller unit 440 supports several antenna pointing aids. Forexample, the controller unit 440 provides a ZIP code to azimuth andelevation calculation. This software application takes a ZIP code as aninput through, for example, the keyboard interface 480, performs thenecessary mathematical calculations or look-up actions, and gives theuser the antenna pointing angles needed to find the satellite signal(azimuth and elevation).

14. Interrupts

The controller unit 440 uses various software routines in response tointerrupt signals. For example, an interrupt may indicate that thewatchdog timer has expired and, as such, the controller unit 440software begins an orderly soft reset procedure. The controller unit 440also utilizes interrupts to service real time clock, serial portcommunications, parallel port communications, keyboard interfacecommunications, and mouse interface communications. All of theseinterfaces generate interrupts that are handled by the operating system.

15. Diagnostics

The controlling unit software supports multiple forms ofself-diagnostics. Some of the diagnostics run on power up to verifysystem integrity, and other diagnostic functions are run periodicallywhile the controller unit 440 is operational. For example, thecontroller unit 440 initially runs several diagnostics including amemory test, a virus scan, a File Allocation Table (FAT) check, abackplane LAN 532 connectivity test, and an external 100 based-T LAN 240interface test when power is first supplied. As part of its ongoingmonitoring process, the controller unit 440 also performs hard drive 455integrity tests to verify that the file system has not been corrupted.If a hard drive error is encountered, the controller unit 440 logs theerror into its trace history, and tries to correct the problem viadownloading of any corrupted files from the Network Operations Center472. Still further, the controller unit 440 monitors the fault status ofevery transponder unit 445 with which it is associated in the respectiveIPMS 120. The fault monitoring status is an on-going periodic process.All faults are preferably entered into a trace buffer that is availablefor history tracking. Each fault will be time-stamped and stored innon-volatile memory.

16. Security

The software of the controller unit 440 supports multiple levels ofsecurity, using passwords. The types of levels of access includes ISPmonitoring, ISP configuration. network operations monitoring, networkoperations configuration, and administrative operations. Each level ofaccess has a unique password. The highest levels of authorization willhave passwords that preferably change periodically. Any changes toeither passwords or configuration settings of the controller unit 440preferably requires a confirmation (either in the form of a Yes/Noresponse or another password).

Command Set for Interfacing With the Controller Unit 440

As noted above, commands can be provided to the controller unit 440through the RS-232 port 487, the 100 based-T LAN network interface card467, the 10 based-T backplane LAN network, interface card 465, orthrough the modem 470. Through the 100 based-T network card 467,commands can be issued either through a SNMP interface, an HTTPinterface, or raw commands through TCP/IP. Exemplary commands are setforth and described below.

1. TCP/IP Address

The TCP/IP address of the IRMS 120 can be set or queried. This commandmay be sent from an interface other than the LAN connection (since theLAN connectivity depends on this parameter).

2. RS-232 Settings

The settings for the COM port can be either queried or configuredthrough the command interface.

3. Table Download

The network provisioning tables are downloaded via a table downloadfacility. This command is used to process all new tables andreconfigures the system as necessary. The tables are described above.

4. Set Transponder Characteristics (per unit)

The controller unit 440 keeps track of which transponder unit 445 isassigned to each transponder. This implies that the RF parameters of thetransponder units 445 are maintained and configured through thecontroller unit 440. Once the user has changed a parameter, thecontroller unit 440 forwards the changed information to the transponderunit 445 via the backplane of the LAN 145.

5. Network Utilization

Several statistics are kept on the network utilization, including theabsolute data rate being output onto the LAN 220 and the numbercollisions being encountered on the LAN 220. The network utilizationstatistics may be made available through a “Network Utilization” querycommand.

6. Maximum LAN Data Rate

The Maximum LAN Data Rate command may be used to limit the amount ofbandwidth that the controller unit 440 uses on the LAN 220. This allowsthe ISP to control the maximum impact that the system has on the LANbackbone.

7. Current Status

The controller unit 440 maintains its own internal status and, further,monitors the status of all of the transponder units 445 cards on the LAN145. The current status of the IPMS 120, and all of its individualmodules, can be queried through the Current Status Command.

8. Card Configuration

The Card Configuration command is used to query the number oftransponder units 445 in the IPMS 120 and their current settings.

9. Usage Statistics

The Usage Statistics command is used to retrieve the current and paststatistics of the channel usage experienced by the IPMS 120. Thisincludes the number of viewers per channel, the usage of a given channelper time, the overall usage of the system per time, and the LANcongestion over time. All of these statistics may be made availablegraphically through an HTTP server or downloaded to the NOC in a binaryform using SNMP.

10. Trace

The Trace command is used to start, stop, and configure the tracefunctions of the controller unit 440. Individual events can be enabledor disabled to further customize the trace capabilities of the unit 440.The trace may be uploaded to the Network Operations Center 472 fordiagnostic purposes. The trace data may be stored on the hard drive,which provides a non-volatile record of the events. The maximum size ofthe trace log is determined by the available space on the hard disk and,preferably, can be selected by the user.

The transponder unit 445 is designed to receive, for example, an L-Bandsignal off of the satellite 55, convert the signal into its originaldigital form, and put the resulting digital signal onto the ISP's 100BTLAN 220. Each IPMS 120 may include multiple transponder units 445thereby allowing the IPMS 120 to handle significant data traffic.

FIG. 18 illustrates various functional blocks of a transponder unit 445.The transponder unit 445 includes an input 550 for receiving an RFsignal, such as the L-band signal from satellite 55. The RF signal issupplied from the input 550 to the input of a demodulator 555 thatextracts the digital data from the RF analog signal. The digital datafrom the demodulator 555 is optionally supplied to the input of adescrambler 560 that decrypts the data in conformance to the manner inwhich the data was, if at all, encrypted at the transmission site.

One embodiment of a descrambler 560 is illustrated in FIG. 19. In theillustrated embodiment the descrambler 560 may be implemented by a fieldprogrammable gate array. One type of field programmable gate arraytechnology suitable for this use is a Lattice ISP 1016.

The descrambler 560 preferably automatically synchronizes to the startof a DVB frame marker provided by the demodulator 555. The descrambler560 receives digital data from the demodulator 555 along data bus 565, aclock signal along one or more lines 570, and a data valid signal alongone or more lines 575. The data valid signal is used to qualify theclock signal in the descrambler 560. The descrambler 560 of theillustrated embodiment should have the capability of processing fourmegabytes/second. Such a processing rate is based on a maximum systemdata rate of 32 bits/second.

The descrambler 560 is also provided with a microprocessor interface forprogramming and monitoring the status of the device by a microprocessor580 (see FIG. 18) such as a Motorola 860 type processor. The descrambler560 preferably supports normal bus access in addition to data transfersthrough the device into the one packet FIFO. The descrambler 560 canalso issue an interrupt to the microprocessor 580 to request immediateservice.

Using a microprocessor interface 585 to the descrambler 560, themicroprocessor 580 is provided with access to the internal registers ofthe descrambler 580 via a bi-directional data bus. The microprocessor580 accesses the device's registers via the address bus of themicroprocessor interface. Preferably, the microprocessor 580 gainsaccess to the registers of the descrambler 560 using a RDNVR signalqualified by a CS signal consistent with the Motorola 860 busarchitecture. The descrambler 560 can also issue an interrupt to the 860processor using INT signal. The microprocessor 580 may also be used toperform overall fuse programming of the descrambler 560 when thedescrambler is implemented using a field programmable gate array.

The descrambler 560 takes the data received on a data bus 565 from thedemodulator 555, de-scrambles it in a manner consistent with anyscrambling operation performed on the data at the transmission site, andprovides it to the input of an HDLC controller 590. In the illustratedembodiment, the descrambler 560 and the HDLC controller 590 interfacewith one another over an HDLC bus 595 that is preferably comprised of anHDLC parallel data bus, a clock signal, and a control bus. The HDLCcontroller 590 serializes the data received on the data bus of the HDLCbus 595 and provides it as a serialized output at serial bus 600 forsupply at one or more output lines. The serial form of the data is usedby the HDLC controller 590 for validation and de-packetizationoperations.

The descrambler 560 may have two modes of operation: a descramble modeand a clear channel mode. In the descramble mode, the device descramblesthe data to be serialized for the HDLC controller 590. Preferably, thedescrambler 560 supports simple P/N sequenced descrambling. This mode isused as a protected transmission mode that assists in preventingunauthorized access of the transmissions. In this mode, the descramblermay use, for example, an 8 bit seed used to descramble the input data.This seed is preferably programmed into the descrambler 560 through themicroprocessor interface bus 605. The microprocessor 580 mayasynchronously set the seed value by writing to a seed resister internalto the descrambler 560.

In the clear channel mode, the descrambler 560 allows the data to beserialized without de-scrambling. This mode is used for an unprotectedtransmission mode in which unauthorized receipt of the transmission isnot a significant issue. Clear channel mode can be set by programmingthe seed register to, for example, all zeros.

The descrambler 560 may also maintain several counters to allow themicroprocessor to detect system errors. For example, the descrambler 560may store a count of the number of block errors detected. This ispreferably implemented as a 16 bit register that rails (i.e. does notcycle back to zero) at OxFFFF (65,535). The descrambler 560 stores acount of the number of valid packets read from the IF.

The HDLC controller 590 receives the parallel bit data from thedescrambler and depacketizes the HDLC frames. The HDLC controller 590processes the CRC, removes the flags, and removes any bit stuffingcharacters from the HDLC frame. If there are any errors in the data theyare indicated in the status provided by the HDLC controller 590. Typicalerrors include CRC errors and frames that are too long. The resultingdata is fed to a FIFO 610 with both start of packet (SOP) and end ofpacket (EOP) indications. The resulting packets stored in FIFO 610 arecomplete TCP/IP packets that can be output onto the 100 BT LAN 220 If apacket contains a CRC error, the packet will be discarded and a packeterror counter will be incremented.

The data from the FIFO 610 is provided to the input of a packet filter615. The packet filter 615 is preferably implemented using a fieldprogrammable gate array. The packet filter 615 determines whether thedata packet stored in the FIFO 610 is intended for transmission on theLAN 220 or is to be discarded. This decision is made by the packetfilter 615 based on whether someone directly connected to the LAN 220 orwho is remotely connected to the LAN 220 has joined the multicast groupto which the packet belongs. The packet filter 615 stores valid packetsinto a single packet FIFO 620 that is used to buffer the packet forprovision to a network interface card, such as an ethernet controller625. The ethernet controller 625 takes the packet from the FIFO 620 andtransmits it onto the LAN 220 through an ethernet transceiver andtransformer using standard ethernet protocols. Such protocols includecollision detection and re-transmission as well as all preamble and CRCgeneration needed. The output of the ethernet controller 625 is fed,using a standard media independent interface (MII) to an ethernettransceiver 630 that converts the digital packet into an ethernet analogsignal.

A transformer 635 is used to alter the electrical levels of this signalso that it is compatible with the LAN 220 The microcontroller 580configures and monitors this entire process and reports status, logsfaults, and communicates with external systems via the internal 10-basedT backplane LAN 145. In addition to the backplane LAN 145, thetransponder unit 445 can be controlled through a standard RS-232 port637 that, for example, may be used for debuting the unit.

Preferably, the packet filter 615 is a TCP/IP filter implemented using afield programmable gate array. The primary task of the packet filter 615is to filter all IP packets received and to pass only valid packets forwhich a subscriber exists on the network for the multicast transmission.Other tasks that may optionally be performed by packet filter 615 aresuch tasks as IP address translation (see above), notification of themicroprocessor of the occurrence of any over flow errors on the channel,etc.

FIG. 20 illustrates one embodiment of the packet filter 615 asimplemented by a field programmable gate array 645 and a static RAM 650.The figure also illustrates the relationship between the packet filter615 and other system components. The field programmable gate array maybe one such as is available from XILINX, LATTICE, ALTERA, or other FPGAmanufacturers.

As illustrated, the packet filter 615 includes a microprocessorinterface 655 comprised of a microprocessor data bus, microprocessoraddress bus, and a microprocessor control bus. The microprocessorinterface 655 provides an interface for programming and monitoring thestatus of the packet filter 615. The device supports normal bus accessin addition to data transfers through the device into the one packetFIFO 610. The packet filter 615 may also issue an interrupt to themicroprocessor 580 to request immediate service.

The microprocessor 580 accesses the registers of the programmable gatearray 645 through the bidirectional data bus of the interface 655.Selection of which of the registers are accessed is performed by themicroprocessor 580 over the address bus of the interface 655. Themicroprocessor 580 gains access to the registers over the control bus ofthe interface 655 using a RDIWR signal that is qualified with a CSsignal consistent with the Motorola 860 bus architecture. Any interruptfrom the packet filter 615 is also provided over the control bus.

The field programmable gate array 645 also provides an SRAM interface660 for interfacing with SRAM 650. This interface is comprised of a databus, an address bus, and a control bus. The gate array 645 gains accessto the registers of the SRAM 650 by selecting the appropriate resisterover the address bus and providing a OE/WR signal qualified by a CSsignal consistent with the SRAM bus architecture.

The field programmable gate array 645 provides packet flow controlbetween the FIFO 620 and FIFO 610. This control is provided based on aFIFO interface that includes a data bus 665 and a FIFO control bus 670.

In the disclosed embodiment, the packet filter 615 is designed to storeup to 64K (65,535) addresses that are used as filter addresses. The LSB(bottom 16 bits) of the 32-bit address field of a packet is compared toan addresses stored in SRAM 650. The addresses in SRAM 650 are storedbased on commands received by the packet filter 615 from themicroprocessor 580. These addresses correspond to multicast groupaddresses for which a subscriber on the system has issued a “join”command. If the address of a packet received at FIFO 610 matches ajoined address stored in the SRAM 650, then the entire packet will bepassed to the single packet FIFO 610 and the FPGA 645 will notify theEthernet controller 625 that the data is to be transmitted onto the LAN220. The single packet FIFO 610 is used as temporary storage until theentire TCP/IP packet is processed and transmitted to the ethernetcontroller 625. If a re-transmit is needed, then the single packets FIFO610 is reset and the data can be read again.

The packet filter 615 auto-synchronizes to the HDLC start of framemarker. This marker is read from the FlFO 620 and the ninth bit is usedto signal the FPGA 645 to re-synchronize the internal state machine.

In the event that the ethernet controller 625 cannot successfullytransmit the packet stored in the single packet FIFO 610, the packetfilter 615 either initiates a re-transmit cycle or aborts the packet andcontinues with the next available packet. To make this determination,the packet filter 615 queries the FIFO 620 for a half-full status. Ifthe FIFO 620 is more that half full, then the packet in the singlepacket FIFO 610 is discarded. If the FIFO 620 is more than half full,then the single packet FIFO 610 is placed in a re-transmit mode and thepacket is given another chance for transmission.

The packet filter 615 may also include a pass-through mode of operation.In this mode the packet filter 615 allows the microprocessor 580 towrite data into the single packet FIFO 610 for application to theethernet controller 625 and, therefrom, for transmission on the LAN 220.This mode may be used to send test packets to the ethernet controller625 and to the client sub-system.

The packet filter 615 may maintain several counters to allow themicroprocessor 580 to detect system errors. Such counters may include acounter for demodulator block errors, a counter for packet re-transmiterrors, a counter for packet abort errors, a counter for valid packetcount, and a counter for valid address count. Each of these counters maybe reset through commands issued from the microprocessor 580 to thepacket filter 615.

The demodulator block error counter is used to count the number of blockerrors that are detected. This counter may be a 16 bit register thatrails at OxFFFF.

The packet re-transmit error counter stores a count of the number ofpackets that the packet filter 615 tried to re-transmit. If a packet isretransmitted more than once, each attempt increments the count. Thiscounter is preferably implemented as a 16 bit register that rails atOxFFFF (65,535).

The packet abort error counter stores a count of the number of packetaborts that have occurred. This is the packets that were notsuccessfully transmitted. This is a 16 bit register that rails (i.e. notcycle back to zero) at OxFFFF (65,535).

The valid packet counter stores a count of the number of valid packetsread from FIFO 620 while the valid address counter stores a count of thenumber of valid TCP/IP addresses received. Each of these counters ispreferably implemented as a 32 bit register counter

Table 1 below describes some of the write registers that may be includedin the packet filter 615, while Table 2 (below Table 1) describes someof the read registers that may be included.

TABLE 1 WRITE REGISTERS REGISTER Size MNEMONIC (bits) DescriptionRAMADDRH 8 SRAM address High RAMADDRL 8 SRAM address Low RAMDATA 5 SRAMData Bit 0 - Filter ON/OFF Bit 1..4 - Translation Address (A15..A12) ofthe TCP/IP address CONTROLREG 8 Miscellaneous control register Bit 0 -Micro pass-through mode Bit 1 - Address Translation ON/OFF Bit 2 -unassigned Bit 3 - unassigned Bit 4 - unassigned Bit 5 - unassigned Bit6 - unassigned Bit 7 - unassigned STATREG 8 Status Register Clear Bit0 - Clear DMERRCNT Bit 1 - Clear RETXCNT Bit 2 - Clear ABORTCNT Bit 3 -Clear PKTCNT Bit 4 - Clear ADDRCNT Bit 5 - unassigned Bit 6 - unassignedBit 7 - unassigned MACADDR0 8 Ethernet Controller Address BYTE 0 (LSB)MACADDR1 8 Ethernet Controller Address BYTE 1 MACADDR2 8 EthernetController Address BYTE 2 MACADDR3 8 Ethernet Controller Address BYTE 3MACADDR4 8 Ethernet Controller Address BYTE 4 MACADDR5 8 EthernetController Address BYTE 5 (MSB)

TABLE 2 READ REGISTERS REGISTER Size MNEMONIC (bits) Description STATREG8 Indicates status of packet filter Bit 0 - Input OVERFLOW Bit I -Single Packet FIFO Timeout Bit 2 - Re-Transmit OVERFLOW Bit 3 -unassigned Bit 4 - unassigned Bit 5 - unassigned PKTSTAT 16 Last packettransmitted status DMERRCNT 16 Demodulator Error Count RETXCNT 16Re-Transmit Count ABORTCNT 16 Packets Aborted Count PKTCNT 32 ValidPackets Count ADDRCNT 32 Valid Packets Count

Table 3 (below) provides an exemplary pin-out listing for the packetfilter 615:

TABLE 3 SIZE PIN NAME(S) (BITS) TYPE DESCRIPTION MICROPROCESSORINTERFACE DATA 8 Input/output Microprocessor data bus ADDRESS 4 InputMicroprocessor data bus CS 1 Input Microprocessor chip select RW 1 InputMicroprocessor read/write INT 1 Output Microprocessor interrupt FIFO 620INTERFACE DATA 8 Input FIFO data input RD 1 Output FIFO read WR 1 OutputFIFO write ERR 1 Input FIFO block error BCLK 1 Input FIFO byte clockBLKSTART 1 Input FIFO start of block FULL I Input FIFO full flag HALF 1Input FIFO half full flag EMPTY 1 Input FIFO empty flag SRAM INTERFACEADDRESS 16 O SPAM address DATA 8 I/O SRAM data RW 1 Output SRAMread/write OE 1 Input SRAM output enable SINGLE PACKET FIFO INTERFACEDATA 9 Output FIFO data RD I Output FIFO read WR 1 Output FlFO write RST1 Output FIFO reset FULL 1 Input FIFO full flag EMPTY 1 Input FIFO emptyflag

As noted above, the packet filter 615 may allow each filtered address tobe translated into another IP address. Translation is preferably onlyallowed on the upper nibble of the LSB (A15, A14, A13, and A12). Thetranslation bits will be downloaded along with the address filterinformation. Still further, the packet filter 615 preferably uses anFPGA 645 that is capable of being modified by the microprocessor 580. Insuch instances, the FPGA technology of the FPGA 645 should be chosen toallow local re-programming of the FPGA fuse map.

The FPGA 645 preferably processes at least one mega-words per second (32bits per word). If the FPGA 645 is run at 10 MHz, then 10 internalcycles can be used in a state machine per word received. A shutdownrelay or other type of physical device may be employed to shut the 100based T LAN output off. This may be controlled by the microprocessor 580and is preferably tied, via backplane communications, to the PanicButton on a front panel of the system. This relay is not shown in thefigures.

The transponder unit 445 of the disclosed embodiment processes a 10BaseT ethernet connection that necessitates a TCP/IP protocol stack.This stack requirement makes it preferable to use a DRAM in thetransponder unit 445. The stack requirement drives the DRAM memoryrequirements of the unit 445. The DRAM should be large enough to supportthe software (the code will be downloaded into DRAM using a TFTP boot),the RAM variables, and the protocol stacks.

The transponder unit 445 also preferably includes a battery backed RAMthat maintains a small trace buffer, factory test results, and thecard's serial number. The non-volatile memory is preferably organizedinto two identical blocks which are both, individually, subject to CRCchecks. Such checks ensure that if a write process is being performedand the power is removed, damaging the integrity of the block, a secondbackup image of the non-volatile memory will still be intact.

Each transponder unit 445 preferably includes a test LED, a fault LED, acarrier sync LED, a LAN activity LED, and a LAN collision LED. The testLED is on whenever the unit is performing a test function, including itspower up test. The fault LED will be on whenever a major fault hasoccurred. The carrier sync LED is activated on whenever the RF signalreceived by the transponder unit 445 is being correctly demodulated andthe data is error free.

The LAN activity LED is activated on whenever the transponder unit 445is actively outputting a multicast stream onto the 100 based-T LAN. TheLAN collision LED indicates a collision has occurred on the 100 based TLAN.

Transponder Unit Software Operation

The transponder unit 445 is preferably controlled by an embeddedsoftware application. The software is responsible for configuring thehardware of the transponder unit 445, monitoring all activity of thetransponder unit 445, and processing any backplane communications. Thefollowing sections describe the various interfaces and tasks that thesoftware supports.

1. Operating System

The underlying real time operating system (RTOS) is preferably VxWorks.VxWorks has been used in embedded processor designs for over 18 yearsand provides a pre-emptive operating environment with an integratedprotocol stack and other types of networking support.

2. Backplane Host Interface

The host interface over the backplane is implemented on a 10 based-Tethernet LAN 145 and the LAN protocol is TCP/IP. All commands that areissued over the backplane LAN 145 are processed identically to commandsreceived over the RS-232 serial interface 487. The controller unit 440transmits commands to the transponder unit 445 over this interface.Still further, the controller unit 440 passes commands from the NOC 472to the transponder unit 445. In order, to support this interface, theoperating system's standard networking protocols are used.

3. RS-232 Serial Command Interface

The serial port 637 is used to provide a diagnostic port that can beused to send commands to the transponder unit 445. The serial portsoftware processes commands identically to the backplane host interface.

4. Command Processor

The command-processing task parses incoming commands and executes anyactions specified by the command.

The following sections (A-N) describe some example commands that thetransponder unit 445 supports:

A. Add Group

The Add Group command allows the controller unit 440 to enable a groupaddress to be passed through to the 100 based-T LAN 220. When thiscommand is executed, the microcontroller 640 enables the group's addresswithin the lookup table in the SRAM 650.

B. Delete Group

The Delete Group command allows the transponder unit 445 to disable agroup address that is currently being passed through to the 100 based-TLAN 220. When this command is executed, the microcontroller 655 disablesthe group's address within the lookup table in the SRAM 650.

C. Address Route

The Address Route command is used to change the default IGMP address ofa particular service or block of services. As described previously, theentire address block allocated to the video from the satellite can bemoved or individual channel addresses can be moved. The transponder unit445 is programmed with an address map and programs the FPGA 650accordingly.

D. LAN Shutoff

The LAN shutoff command activates a relay on the output to the 100based-T LAN 220 The controller unit 440 issues this command when thePanic Button has been pressed.

E. RS-232 Port

The RS-232 Port command is used to change the communication portparameters. These parameters include the baud rate, parity bit, stopbit, and number of data bit settings for the port.

F. Boot

A TFTP process, initiated by the operating system of the transponderunit 445 will handle the boot process. This process is handled over thebackplane LAN 145.

G. Status and Fault

The current status and fault histories can be queried through the Statusand Fault commands. These commands are accessed by the controller unit440, the NOC 472, and through the RS-232 port 675 to determine thestatus and fault histories of the transponder unit 445.

H. Trace

Similar to the trace command on the controller unit 440, the tracecommand of the transponder unit 445 can be used to configure (start,stop, or reset) the trace buffer, or it can be used to query thecontents of a trace buffer. The trace buffer on the transponder unit 445may be implemented to be much smaller than the trace buffer of thecontroller unit 440 so the controller unit 440 accesses data from thetrace buffer of the transponder unit 445 periodically, resetting thetrace after the query is complete.

I. Set Carrier

The Set Carrier command is used to set the L-Band frequency and datarate of the demodulator 555. Once this command has been issued, thetransponder unit 445 begins its acquisition process.

J. Scrambler Bypass

The Scrambler Bypass command allows the transponder unit 445 to passdata through the system that has not been scrambled at the head end.This mode is used during development, testing, and may be used inoperation.

K. Reset

The Reset command allows an external source, such as the controller unit440, the NOC 472, or a terminal attached to the RS-232 port to initiatea soft reset on the transponder unit 445.

L. ID Query

Each transponder unit 445 will have a unique serial number associatedwith it. The serial number will be stored in non-volatile memory. The IDQuery command is used to either query or set the serial number. Whensetting the serial number, the command is preferably sufficientlyscrambled to prevent the serial number from being inadvertentlyprogrammed to an incorrect value.

M. Memory Read and Memory Write

The Memory Read and Memory Write commands are used primarily fordevelopment and allows any hardware register or memory location to bemanipulated manually. This includes being able to toggle LED's, updatethe seven-segment LED, or other I/O based activities.

N. Test Mode

The Test Mode command provides a means of putting various components ofthe transponder unit 445 into test modes. For example, one test modegenerates test packets onto the 100 based-T output LAN. These packetsinclude a packet counter which can be used by a client application todetermine if the link is experiencing dropped packets. This command mayalso be used during board level testing with the results of theproduction tests stored in nonvolatile memory.

The transponder unit 445 is also provided with a number of diagnosticfunctions that support both power up and long-term diagnostic functions.On power up, all hardware subsystems are tested including the DRAM, thenon-volatile memory, communications with the demodulator, and backplaneethernet connectivity. Long term diagnostic functions include validatingthe code space (CRC check of the code space), validating thenon-volatile memory, and validating backplane connectivity.

On powering up, the operating system of the transponder unit 445 bootsfrom its core from EPROM. After this, the transponder unit 445 requestsits current version of firmware from the controller unit 440 using aTrivial File Transfer Protocol (TFTP). This method of booting thetransponder unit 445 ensures that all transponder units in the IPMSchassis are running the same version of software. The operating system,as noted above, supports this type of boot procedure. Once the code hasbeen downloaded, the code begins executing.

The transponder unit 445 also includes a status and fault monitoringtask that keeps track of the current status as well as a fault historyvalue that indicates all of the faults that have occurred since the lasttime the fault history was cleared. When the status of the transponderunit 445 changes, a trace event is logged into the non-volatile memoryof the transponder unit 445 and the controller unit 440 is notified thatthe transponder unit 445 has at least one event saved in itsnon-volatile memory. Since the controller unit 440 preferably maintainsa much larger trace buffer than the transponder unit 445, the controllerunit 440 is responsible for pulling data out of the log of thetransponder unit 445 prior to overflow thereof.

The transponder unit 445 also includes an internal watchdog timer. Ifthe internal watchdog timer has expired, the transponder unit 445assumes that its internal software has reached an unstable condition. Assuch, the transponder unit 445 will shutdown all current tasks and thenreset. The reset re-initializes the transponder unit 445 and begins are-boot procedure. The transponder unit 445 will preferably log thisevent in non-volatile memory. The controller unit 440 recognizes thiscondition, logs an error, and reconfigures the transponder unit 445.

The transponder unit 445 shuts down the outgoing IGMP streams after thebackplane LAN 145 becomes inoperable for a specified period of time. Ifthe backplane LAN 145 has become inoperable, the transponder unit 445assumes that the controller unit 440 has ceased operation. Since thecontroller unit 440 is responsible for all of the protocol communicationof the IPMS 120 with external devices, the transponder unit 445 assumesthat the controller unit 440 can no longer receive ‘leave’ requests fromclients. In order to prevent “bombarding” the client with potentiallyunwanted data, the transponder unit 445 will shutdown all outgoingstreams.

Once backplane LAN 145 communications are restored, the transponder unit445 will request its current channel mapping and begin transmittingagain. The transponder unit 445 logs this event in non-volatile memory.

Each transponder unit 445 is preferably implemented on a single printedcircuit card having the ability to be “hot swapped”. In order for thisto be implemented, the connectors between the printed circuit card andits corresponding backplane connector include longer pins for the powerand grounds signals such that the transponder unit on the printedcircuit board has power applied to it before output signals reach theconnectors of the backplane bus.

A “hot sparing” system can also be employed. In such instances, one ormore spare transponder units are included in the IPMS 120 chassis. Thespare transponder units can be configured to take over for failedtransponder units. This configuration procedure will be handled by thecontroller unit via the backplane LAN 145.

The IPMS 120 may have several means of helping an installer point theantenna. To this end, each transponder unit 445 provides an AGEindication that provides a means of identifying when the satellitesignal is maximized. This indication alone will not necessarily providethe best signal, however, due to different types of interference(adjacent satellite, cross-pole, etc.). Many times the interferenceshould be minimized instead of the signal level being maximized. To aidin this type of decision making each transponder unit 445 will providean Eb/No reading that indicates the quality of the incoming signal. Thismeasurement should be maximized. The values of these parameters will bepassed to the controller unit 440, which can present them in auser-friendly manner to the installer. This data may also be availablethrough the serial port 637 of the transponder unit 445.

As also illustrated in FIG. 18, the transponder unit 445 also includes a10baseT connection to the controller unit. This interface includes anethernet transceiver 672 and transformer 673. It should be furtherednoted that substantially all of the principal units of the transponderunit 445 communicate with microprocessor 580 over a communications bus.

FIGS. 21-26 illustrate various example ISP configurations and scenariosusing the IPMS 120 of the present invention. In each scenario, an IPMulticast system application delivers IP multicast streams to InternetService Providers' (ISPs) clients. The stream content is received, forexample, over a satellite by the IPMS which is directly attached to anISP's local backbone. The stream flows over the local backbone andthrough the ISP's networking equipment to the client's desktop browseras shown, for example, at arrow 680 of FIG. 21.

There are a number of goals for each of the following ISP configurationsand scenarios. They include:

-   -   Delivering streams to clients on demand, and quickly removing        these streams from the ISP backbone when the client is finished    -   Delivering streams to clients while minimizing the traffic on        the local backbone of the ISP;    -   Delivering streams to clients while minimizing additional        traffic to other clients: and    -   Delivering streams to clients while not introducing any        additional traffic to the Internet.

Achieving these goals requires that the networking equipment utilized inthe system support various protocol interactions (e.g. IP, IGMP, PIM).

ISP Model 1—Simple ISP (Simple IPMS 120)

ISP MODEL 1 is illustrated in FIG. 21. In this example Client A joins,receives, and leaves Multicast Group 239.216.63.248 from the IPMS 120.Next, Client A joins and receives Multicast Group 239.216.0.8. Then,network elements query the group so that multicast traffic can be prunedin the event group members silently leave the group. Finally, Client Aleaves Multicast Group 239.216.0.8.

The IPMS 120 filters the multicast stream so that which are currently“joined will be placed on the ISP LAN several assumptions associatedwith scenario, they are:

-   -   IPMS 120 IP Address128.0.0.255, Client AIP Address=128.0.0.1:    -   All IP Multicast Addresses provided by the IPMS 120 are        “Administratively Scoped” addresses in the range 239.216.0.0        through 239.219.255.255 (addresses 239.216.0.8 and        239.216.63.248 used in this example); and    -   IPMS 120. Access Switch/Routers #1 and #2, and Gateway Router        685 support IGMP V2.

During initial handshake, the following occurs:

-   -   1. Client A sends an IGMP V2 Membership Report (Destination IP        address=239.216.63.248, Group address=239.216.63.248);    -   2. Access Switch/Router #1 forwards IGMP V2 Membership Report to        backbone LAN 220 (assuming it has no other interfaces in Group        address=239.216.63.248);    -   3. Gateway Router does not forward “Administratively Scoped”        membership report to the internet;    -   4. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.63.248 multicast onto Filtered Stream—the data payload        of the 239.216.63.248 multicast includes the IPMS IP Address,        and a test pattern;    -   5. Access Switch/Router #1 forwards 239.216.63.248 multicast to        Client A only;    -   6. Gateway Router ignores 239.216.63.248 multicast as an        administratively scoped address;    -   7. Client A receives IPMS IP Address and test pattern and then        sends an IGMP Leave Group (Destination IP address=224.0.0.2,        Group address=239.216.63.248);    -   8. Access Switch/Router #1 verifies it has no other interfaces        in Group address=239.216.63.248 (using IGMP Query), forwards        IGMP Leave Group to LAN backbone 220, and immediately stops        forwarding the 239.216.63.248 multicast to Client A;    -   9. Gateway Router 685 ignores IGMP Leave Group command; and    -   10. IPMS 120 receives IGMP Leave Group, verifies it has no other        clients in Group address=239.216.63.248 (using IGMP Query), and        immediately stops transmission of the 239.216.63.248 multicast        data.

When Client A joins Multicast Group 239.216.0.8, the following occurs:

-   -   11. Client A sends an IGMP V2 Membership Report (Destination IP        address=239.216.0.8, Group address=239.216.0.8);    -   12. Access Switch/Router #1 forwards IGMP V2 Membership Report        to LAN backbone 220 (assuming it has no other interfaces in        Group address=239.216.0.8);    -   13. Gateway Router ignores IGMP V2 Membership Report for        “Administratively Scoped” address;    -   14. IPMS 120 receives IOMP V2 Membership Report and transmits        239.216.0.8 multicast onto Filtered Stream:    -   15. Access Switch/Router #1 forwards 239.216.0.8 multicast to        Client A only;    -   16. Gateway Router ignores 239.216.0.8 multicast as an        administratively scoped address;    -   17 Client A receives 239.216.0.8 multicast.

In order to ensure that Client A has not silently left the multicastgroup, the system implements a querying of the Multicast Group239.216.0.8 based on query timers configured in the access switch/routerand IPMS 120. This query proceeds in the following manner;

-   -   18. Access Switch/Router #1 sends IGMP Group-Specific Query        (Destination IP address=239.216.0.8, Group address=239.216.0.8)        to Client A;    -   19. If Access Switch/Router #1 receives an IGMP V2Membership        Report (Destination IP address=239.216.0.8, Group        address=239.216.0.8), do nothing;    -   20. If there is no Membership Report then Access Switch/Router        #1 sends IGMP Leave Group (Destination IP address=224.0.0.2,        Group address=239.216.0.8) to the LAN backbone 220 and        immediately stops forwarding the 239.216.0.8 multicast to all        clients (including Client A): system operation then proceeds        with Step 26 below.

The followings steps occur independently:

-   -   21. IPMS 120 sends IGMP Group-Specific Query (Destination IP        address=239.216.0.8, Group address=239.216.0.8);    -   22. If IPMS 120 receives an IGMP V2 Membership Report        (Destination IP Address=239.216.0.8; Group Address=239.216.0.8)        do nothing;    -   23. If there is no Membership Report then IPMS 120 immediately        stops transmission of 239.216.0.8 multicast (group left due to        no response);

The following sequence of events occur when Client A leaves theMulticast Group 239.216.0.8;

-   -   24. Client A sends an IGMP Leave Group(Destination IP        Address=224.0.0.2, Group Address=239.216.0.8);    -   25. Access Switch/Router #1 receives IGMP Leave Group, verifies        it has no other interfaces in Group Address=239.216.0.8 (using        IGMP Query), forwards IGMP Leave Group to LAN backbone 220, and        immediately stops forwarding the 239.216.0.8 multicast to Client        A;    -   26. Gateway Router ignores IGMP Leave Group command since it        involves an administratively scoped address;    -   27. IPMS 120 receives IGMP Leave Group, verifies it has no other        Clients in Group Address=239.216.0.8 (using IGMP Query), and        immediately stops transmission of 239.216.0.8 multicast.

ISP Model 2—ISP with Multiple LAN Segments/Multicast

In the example shown in FIG. 22, Client A joins, receives, and leavesMulticast Group 239.216.63.248 to receive a brief multicast from theIPMS 120. Next, Client A joins and receives Multicast Group 239.216.0.8.Then, network elements query the group so that multicast traffic can bepruned in the event group members silently leave the group. Finally,Client A leaves Multicast Group 239.216.0.8.

The Simple IPMS 120 filters the Multicast Steam so that only MulticastAddresses which are currently “joined” will be sent to the LAN Switch.The LAN Switch filters the Multicast Stream sent to each segment so thatonly Multicast Addresses which are currently “joined” by Clients on asegment will be placed on that segment.

There are several assumptions associated with the illustrated scenario.

They are:

-   -   IPMS 120 IP Address=128.0.0.255, Client AIP Address=128.0.0.1;    -   All IP Multicast Addresses transmitted by the IPMS 120 are        “Administratively Scoped” addresses in the range 239.216.0.0        through 239.219.255.255 (addresses 239.216.0.8 and        239.216.63.248 used in this example);    -   Access Switch/Router, LAN Switch, and IPMS 120 support IGMP V2;    -   LAN Switch configuration:        -   Virtual LAN#1=LAN Segment #1, Backbone, IPMS 120 Control,            Filtered Stream#1        -   Virtual LAN#2=LAN Segment #2, Backbone, IPMS 120 Control,            Filtered Stream#2    -   Gateway Router 690 does not forward IGMP messages with        “Administratively Scoped” Multicast addresses (this includes        messages with Dest IP239.*.*.*, and IGMP messages with Dest        IP224.0.0.1/224.0.0.2 that specify a Group Address=239.**.*).

During initial handshake, the following occurs:

-   -   1. Client A sends an IGMP V2 Membership Report (Destination IP        Address=239.216.63.248, Group Address=239.216.63.248);    -   2. Access Switch/Router #1 forwards IGMP V2 Membership Report to        LAN Segment #1 (assuming it has no other interfaces in Group        Address=239.216.63.248);    -   3. LAN Switch receives IGMP V2 Membership Report, forwards the        message, and enables transmission of 239.216.63.248 multicast to        LAN Segment #1;    -   4. Gateway Router does not forward “Administratively Scoped”        membership report to the Internet;    -   5. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.63.248 multicast out NIC#2 onto Filtered Stream—the data        payload of the 239.216.63.248 multicast includes the IPMS 120 IP        Address, and a test pattern;    -   6. LAN Switch forwards 239.216.63.248 multicast to LAN Segment        #1 only;    -   7. Access Switch/Router #1 forwards 239.216.63.248 multicast to        Client A only;    -   8. Client A receives IPMS 120 IP Address and test pattern and        then sends an IGMP Leave Group(Destination IP Address=224.0.0.2,        Group Address=239.216.63.248);    -   9. Access Switch/Router #1 receives IGMP Leave Group, verifies        it has no other interfaces in Group Address=239.216.63.248        (using IGMP Query), forwards IGMP Leave Group to LAN Segment #1        and immediately stops forwarding the 239.216.63.248 multicast to        Client A;    -   10. LAN Switch receives IGMP Leave Group, forwards the message,        verifies that it has no other LAN Segment #1 Clients in Group        Address=239.216.63.248 (using IGMP Query), and immediately stops        transmission of 239.216.63.248 multicast to LAN Segment #1;    -   11. Gateway Router ignores IOMP Leave Group since it is an        administratively scoped address;    -   12. IPMS 120 receives IGMP Leave Group, verifies it has no other        client in Group Address=239.216.63.248 (using IGMP Query), and        immediately stops transmission of the 239.216.63.248 multicast.

When Client A joins the Multicast Group 239.216.0.8, the followingoperations occur:

-   -   13. Client A sends an IGMP V2 Membership Report (Destination IP        Address=239.216.0.8, Group Address=239.216.0.8);    -   14. Access Switch/Router #1 forwards IGMP V2 Membership Report        to LAN Segment #1 (assuming it has no other interfaces in Group        Address=239.216.63.248);    -   15. LAN Switch receives IGMP V2 Membership Report, forwards the        message, and enables transmission of239.216.0.8 multicast to LAN        Segment #1;    -   16. Gateway Router ignores IGMP Leave Group since it is an        administratively scoped address;    -   17. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.0.8 multicast out NIC#2 onto Filtered Stream;    -   18. LAN Switch forwards 239.216.0.8 multicast to LAN Segment #1        only;    -   19. Access Switch/Router #1 forwards 239.216.0.8 multicast to        Client A only; and    -   20. Client A receives 239.216.0.8 multicast.

In order to ensure that Client A has not silently left the multicastgroup, the system implements a querying of the Multicast Group239.216.0.8 based on query timers configured in the access switch Irouter and IPMS 120. This query, proceeds in the following manner;

-   -   21. Access Switch/Router #1 sends IOMP Group-Specific Query        (Destination IP Address 239.216.0.8, Group Address=239.216.0.8)        to Client A;    -   22. If Access Switch/Router #1 receives an IGMP V2 Membership        Report(Destination IP Address=239.216.0.8, Group        Address=239.216.0.8), do nothing;    -   23. If there is no Membership Report then Access Switch/Router        #1 sends IGMP Leave Group(Destination IP Address=224.0.0.2,        Group Address=239.216.0.8) to LAN Segment #1 and immediately        stops forwarding the 239.216.0.8 multicast to all clients        (including Client A): and operations then proceed at Step 32.

The following steps occur independently:

-   -   24. LAN Switch sends IGMP Group-Specific Query(Destination IP        address 239.216.0.8, Group Address 239.216.0.8) to LAN Segment        #1;    -   25. If LAN Switch receives IGMP V2 Membership Report        (Destination IP Address=239.216.0.8, Group Address=239.216.0.8)        do nothing;    -   26. If there is no Membership Report then LAN Switch sends IGMP        Leave Group (Destination IP Address=224.0.0.2, Group        Address=239.216.0.8) to IPMS 120 and immediately stops        transmission of 239.16.0.8 multicast to LAN Segment #1 (group is        left due to no response);    -   27. IPMS 120 sends IGMP Group-Specific Query (Destination IP        Address=239.216.0.8, Group Address=239.216.0.8);    -   28. If IPMS 120 receives IOMP V2 Membership Report (Destination        IP Address=239.216.0.8, Group Address=239.216.0.8), do nothing;        and    -   29. If there is no Membership Report then IPMS 120 immediately        stops transmission of 239.216.0.8 multicast (group left due to        no response).

The following sequence of events occur when Client A leaves theMulticast Group 239.216.0.8:

-   -   30. Client A sends an IGMP Leave Group (Destination IP        Address=224.0.0.2, Group Address=239.216.0.8);    -   31. Access Switch/Router 1 receives IOMP Leave Group, verifies        it has no other interfaces in Group Address=239.216.0.8 (using        IGMP Query), and forwards IGMP Leave Group to LAN Segment #1 and        immediately stops forwarding the 239.216.0.8 multicast to Client        A;    -   32. LAN Switch receives IGMP Leave Group, forwards the message,        verifies it has no other LAN Segment #1 Clients in Group        Address=239.216.0.8 (using IGMP Query), and immediately stops        transmission of 239.216.0.8 multicast to LAN Segment #1;    -   33. Gateway Router ignores IOMP Leave Group since it is an        administratively scoped address;    -   34. IPMS 120 receives IGMP Leave Group, verifies it has no other        Clients in Group Address=239.216.0.8 (using IGMP Query), and        immediately stops transmission of 239.216.0.8 multicast.

ISP Model 3—Large ISP with Affiliated ISP

The system of FIG. 23 provides multicast streams to all ISP Clients andRemote ISP Clients on demand. In this example. Remote LSD Client Hjoins, receives, and leaves Group 239.216.63.248 to receive a briefmulticast from the IPMS 120. Next, Client H joins and receives MulticastGroup 239.216.0.8. Then, network elements query the group so thatmulticast traffic can be pruned in the event group members silentlyleave the group. Finally, Client H leaves Multicast Group 239.216.0.8.

The Simple IPMS 120 filters the Multicast Stream so that only multicastaddresses that are currently joined” will be sent to the LAN Switch 695.The LAN Switch 695 filters the multicast stream sent to each segment sothat only multicast addresses which are currently “joined” by clients ona LAN segment will be placed on the LAN segment. For the Remote ISP, themulticast streams do not use bandwidth on the Router link to the ISP (toavoid impacting normal Internet traffic). Accordingly, a bridgedconnection 700 is used to send the streams to the Remote ISP. The onlysegments that receive the multicast streams are LAN Segment #1 and thebridged connection 700 to the Remote ISP that is considered to be LANSegment #2.

There are several assumptions associated with the illustrated scenario,such as, for example:

-   -   IPMS 120 IP Address=128.0.0.255, Client H IP Address=128.0.0.8;    -   All IP Multicast Addresses transmitted by the IPMS 120 are        “Administratively Scoped” addresses in the range 239.216.0.0        through 239.219.255.255 (addresses 239.216.0.8 and        239.216.63.248 used in this example);    -   Access Switch/Routers, LAN Switches, and IPMS 120 support IGMP        V2;    -   LAN Switch configuration: Virtual LAN#1=LAN Segment #1.        Backbone, IPMS 120 Control, Filtered Stream#1; Virtual LAN#2=LAN        Segment #2, IPMS 120 Control, Filtered Stream#2; and virtual        LAN#3=LAN Segment #3, Backbone.    -   LAN Bridge configuration: Only forward        239.216.0.0-239.219.255.255; 224.0.0.1, 224.0.0.2;    -   Remote Router does not forward IGMP messages with        “Administratively Scoped” Multicast addresses (this includes        messages with Destination IP=239.*.*.*, and IGMP messages with        Destination IP=224.0.0.1/224.0.0.2 that specify a Group        Address=239.*.**)

During initial handshake, the following occurs:

-   -   1. Client H sends an IGMP V2 Membership Report (Destination IP        Address=239.216.63.248, Group Address=239.216.63.248);    -   2. Access Switch/Router #2 forwards IGMP V2 Membership Report to        Remote Backbone (assuming, it has no other interfaces in Group        Address=239.216.63.248) seminal LAN Bridge forwards IGMP V2        Membership Report;    -   3. Remote Router ignores IGMP V2 Membership Report as an        administratively scoped address    -   4. LAN Switch receives IOMP V2 Membership Report, forwards the        message, and enables transmission of 239.216.63.248 multicast to        LAN Segment #2.    -   5. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.63.248multicast out NIC#2 onto Filtered Stream—the data        payload of the 239.216.63.248 multicast includes the IPMS 120 IP        Address, and a test pattern;    -   6. LAN Switch forwards 239.216.63.248 multicast to LAN Segment        #2 only;    -   7. LAN Bridge forwards the 239.216.63.248 multicast data;    -   8. Access Switch/Router #2 forwards 239.216.63.248 multicast to        Client H only;    -   9. Remote Router ignores 239.216.63.248 multicast data;    -   10. Client H receives IPMS 120 IP Address and test pattern and        then sends an IGMP Leave Group (Destination IP        Address=224.0.0.2, Group Address=239.216.63.248);    -   11. Access Switch/Router #2 receives IGMP Leave Group, verifies        it has no other interfaces in Group Address=239.216.63.248        (using IGMP Query),    -   12. Forwards IGMP Leave Group to LAN Bridge, and immediately        stops forwarding the 239.216.63.248 multicast to Client H;    -   13. LAN Bridge forwards IGMP Leave Group;    -   14. Remote Router ignores IGMP Leave Group as an        administratively scoped address    -   15. LAN Switch receives IGMP Leave Group, forwards the message,        verifies it has no other LAN Segment an Clients in Group        Address=239.216.63.248 (using IOMP Query), and immediately stops        transmission of 239.216.63.248 multicast to LAN Segment #2;    -   16. IPMS 120 receives IGMP Leave Group, verifies it has no other        Clients in Group Address=239.216.63.248 (using IGMP Query), and        immediately stops transmission of the 239.216.63.248 multicast:

When Client H joins the Multicast Group 239.216.0.8, the followingactions occur:

-   -   17. Client H sends an IGMP V2 Membership Report (Destination IP        Address=239.216.0.8, Group Address=239.216.0.8);    -   18. Access Switch Router #2 forwards IGMP V2 Membership Report        to Remote Backbone (assuming it has no other interfaces in Group        Address=239.216.0.8);    -   19. LAN Bridge forwards IGMP V2 Membership Report;    -   20. Remote Router ignores IGMP V2 Membership Report as an        administratively scoped address;    -   21. LAN Switch receives IOMP V2 Membership Report, forwards the        message, and enables transmission of 239.216.0.8 multicast to        LAN Segment #2;    -   22. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.0.8 multicast out NIC#2 onto Filtered Stream;    -   23. LAN Switch forwards 239.216.0.8 multicast to LAN Segment #2        only;    -   24. LAN Bridge forwards the 239.216.0.8 multicast;    -   25. Access Switch/Router #2 forwards 239.216.0.8 multicast to        Client H only;    -   26. Remote Router ignores 239.216.0.8 multicast    -   27. Client H receives 239.216.0.8 multicast.

In order to ensure that Client H has not silently left the multicastgroup, the system implements a querying of the Multicast Group239.216.0.8 based on query timers configured in the access switch Irouter and IPMS 120. This query proceeds in the following manner:

-   -   28. Access Switch/Router #2 sends IGMP Group-Specific Query        (Destination IP address=239.216.0.8, Group Address=239.216.0.8)        to Client H;    -   29. If Access Switch/Router #2 receives an IGMP V2 Membership        Report (Destination IP Address=239.116.0.8, Group        Address=239.216.0.8), do nothing;    -   30. If there is no Membership Report then Access Switch/Router        #2 sends JGMP:    -   Leave Group (Destination IP Address=224.0.0.2, Group        Address=239.216.0.8) to Remote Backbone and immediately stops        forwarding the 239.216.0.8 multicast to Client H, operations        then proceed to Step 40.

The following steps occur independently:

-   -   31. LAN Switch sends IGMP Group-Specific Query (Destination IP        Address 239.216.0.8, Group Address=39.216.0.8) to LAN Segment        #2;    -   32. LAN Bridge forwards IGMP Group-Specific Query;    -   33. If LAN Switch receives an IGMP V2 Membership Report        (Destination IP Address=239.216.0.8, Group Address=239.216.0.8),        do nothing;    -   34. If there is no Membership Report then LAN Switch immediately        stops transmission of 239.216.0.8 multicast to LAN Segment #2        (group is left due to no response);    -   35. IPMS 120 sends IGMP Group-Specific Query (Destination IP        Address=239.216.0.8, Group Address=239.216.0.8)    -   36. If IPMS 120 receives IGM V2 Membership Report (Destination        IP Address=239.216.0.8, Group Address=239.216.0.8), do nothing;    -   37. If there is no Membership Report then IPMS 120 immediately        stops transmission of 239.216.0.8 multicast (group left due to        no response).

The following sequence of operations occur when Client H leaves Groupaddress=239.216.0.8:

-   -   38. Client H sends an IGMP Leave Group (Destination IP        Address=224.0.0.2, Group Address=239.216.0.8);    -   39. Access Switch/Router receives IGMP Leave Group, verifies it        has no other interfaces in Group Address=239.216.0.8 (using IGMP        Query), and forwards IGMP Leave Group to Remote Backbone and        immediately stops forwarding the 239.216.0.8 multicast to Client        H.    -   40. LAN Bridge forwards IGMP Leave Group;    -   41. Remote Router ignores IOMP Leave Group since it is an        administratively scoped address;    -   42. LAN Switch receives the IGMP Leave Group command, forwards        the message, verifies it has no other LAN Segment #2 Clients in        Group Address=239.216.0.8, and immediately stops transmission of        239.216.0.8 multicast to LAN Segment #2;    -   43. IPMS 120 receives IOMP Leave Group, verifies it has no other        Clients in Group Address=239.216.0.8 (using IGMP Query), and        immediately stops transmission of the 239.216.0.8 multicast.

If Remote Clients join “normal” multicast groups (i.e., thosetransmitted over the backbone of the Internet) through the RemoteRouter, the 224.0.0.1 and 224.0.0.2 IGMP V2 messages will be bridged tothe LAN Switch. The LAN Switch forwards the IGMP messages through LANsegment #2 to the IPMS 120. The IPMS 120 ignores the messages issued fora non-existent stream.

ISP Model 4—Simple ISP Scenario 2

In the scenario of FIG. 24. Client A and the IPMS 120 first joinMulticast Group 239.216.63.240 to establish a mechanism for sendingmulticast control messages to each other. Next, Client A joins,receives, and leaves Multicast Group 239.216.63.248 to receive a briefmulticast from the IPMS 120. After that, Client A joins and receivesMulticast Group 239.216.0.8. Then, network elements query the group sothat multicast traffic can be pruned in the event group members silentlyleave the group. Finally, Client A leaves Multicast Group 239.216.0.8.As above, IPMS 120 filters the multicast stream so that only multicastaddresses which are currently ‘joined’ are provided on the backbone ofthe LAN.

In this scenario, several assumptions have been made. They, are:

-   -   IPMS 120 IP Address=128.0.0.255, Client A IP Address=128.0.0.1;    -   All IP Multicast Addresses transmitted by the IPMS 120 are        “Administratively Scoped” addresses in the range 239.216.0.0        through 239.219.255.255 (addresses 239.216.0.8, 239.216.63.24        through 239.216.63.248 being used in this example);    -   IPMS 120, Access Switch/Routers, and Gateway Router support IGMP        V2 protocol;    -   The IPMS 120 and the clients use MulticastAddress=239.216.63.240        to pass proprietary UDP packets using UDP Port=255.

The following operations occur during initial handshake:

-   -   1. IPMS 120 sends an IGMP V2 Membership Report (Destination P        Address=239.216.63.240, Group Address 239.216.63.240);    -   2. The 239.216.63.240 multicast will be used for multicast        control messages;    -   3. Gateway Router does not forward “Administratively Scoped”        membership report to the Internet;    -   4. Client A sends an IGMP V2 Membership Report (Destination IP        Address=239.216.63.240, Group Address=239.26.63.240);    -   5. Access Switch/Router #1 forwards IOMP V2 Membership Report to        LAN Segment#1 (assuming it has no other interfaces in Group        Address=239.216.63.240);    -   6. LAN Switch receives IGMP V2 Membership Report, forwards the        message, and adds Client A to the Group;    -   7. Gateway Router does not forward “Administratively Scoped”        membership report to the Internet;    -   8. IPMS 120 receives IGMP VI Membership Report; the        239.216.63.240 multicast will be used for multicast control        messages;    -   9. Client A sends an IOMP V2 Membership Report (Destination IP        Address=239.216.63.248, Group Address239.216.63.248);    -   10. Access Switch/Router #1 forwards IGMP V2 Membership Report        to backbone (assuming it has no other interfaces in Group        Address=239.216.63.248);    -   11. Gateway Router does not forward “Administratively Scoped”        membership report to the Internet;    -   12. IPMS 120 receives IGNIP V2 Membership Report and transmits        239.216.63.248 multicast out NIC#2 onto Filtered Stream—the data        payload of the 239.216.63.248 multicast includes the IPMS 120 P        Address, and a test pattern;    -   13. Access Switch/Router #1 forwards 239.216.63.248 multicast to        Client A only;    -   14. Gateway Router ignores 239.216.63.248 multicast since it is        an Administratively scoped address;    -   15. Client A receives IPMS 120 IP Address and test pattern and        then sends an IGMP Leave Group (Destination IP        Address=224.0.0.2, Group Address=239.216.63.248);    -   16. Access Switch/Router #1 verifies it has no other interfaces        in Group Address=239.216.63.248 (using IGMP Query), forwards        IGMP Leave Group to backbone, and immediately stops forwarding        the 239.216.63.248 multicast to Client A;    -   17. Gateway Router ignores IGMP Leave Group command since it is        on an administratively scoped address;    -   18. IPMS 120 receives IGMP Leave Group, verifies it has no other        Clients in Group Address=239.216.63.248 (using IGMP Query), and        immediately stops transmission of the 239.216.63.248 multicast;    -   19. Client A sends a UDP packet (Destination IP        Address=28.0.0.255, Port=255) to the IPMS 120;    -   20. Access Switch/Router #1 forwards UDP packet to backbone;    -   21. Gateway Router does not forward packet to Internet since it        is destined for a local administratively scoped address;    -   22. IPMS 120 receives UDP packet and sends UDP packet        (Destination IP Address=128.0.0.1, Port=255);    -   23. Gateway Router does not forward packet to Internet since it        is destined for a local administratively scoped address;    -   24. Access Switch/Router #1 forwards UDP packet to Client A;    -   25. Client A receives UDP packet.

The following operations occur when Client A joins Multicast Group239.216.0.8:

-   -   26. Client A sends an IGMP V2 Membership Report (Destination IP        Address=239.216.0.8, Group Address=239.216.0.8);    -   27. Access Switch/Router #1 forwards IGMP V2 Membership Report        to the LAN backbone(assuming it has no other interfaces in Group        Address=239.216.63.248).    -   28. Gateway Router ignores IGMP V2 Membership Report since it is        an administratively scoped address;    -   29. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.0.8 multicast out NIC2 onto Filtered Stream;    -   30. Access Switch/Router #1 forwards 239.216.0.8 multicast to        Client A only;    -   31. Gateway Router ignores 239.216.0.8 multicast        (“Administratively Scoped” address);    -   32. Client A receives 239.216.0.8 multicast.

The following query operations ensure that the IPMS 120 does nottransmit a Multicast Group that a client has silent left:

-   -   33. Access Switch/Router #1 sends IGMP Group-Specific Query        (Destination IP Address=239.216.0.8, Group Address=239.216.0.8)        to Client A    -   34. If Access Switch/Router #1 receives an IGMP V2 Membership        Report (Destination IP Address=239.216.0.8, Group        Address=239.216.0.8), do nothing;    -   35. If there is no Membership Report then Access Switch/Router        #1 sends IGMP Leave Group(Destination IP Address=224.0.0.2,        Group Address=2239.216.0.8) to backbone and immediately stops        forwarding the 239.216.0.8) multicast to all Clients (including        Client A): operations then proceed at Step 40;    -   36. IPMS 120 sends UDP packet(Destination IP        Address=239.216.63.240, Port=255);    -   37. Client A receives UDP packet and responds with UDP packet        (Destination IP Address=239.216.63.240. Port=255) (other Clients        will receive and ignore this packet);    -   38. If IPMS 120 receives no UDP response, then it immediately        stops forwarding the 239.216.0.8 to all Clients (group left due        to no response).

The following operations occur when Client A purposely leaves the Group;

-   -   39. Client A sends an IGMP Leave Group (Destination IP        Address=224.0.0.2, Group Address=239.216.0.8);    -   40. Access Switch/Router #1 receives IGMP Leave Group, verifies        it has no other interfaces in Group Address=239.216.0.8 (using        IGMP Query), forwards IOMP Leave Group command to the LAN        backbone, and immediately stops forwarding the 239.216.0.8        multicast to Client A;    -   41. Gateway Router ignores the IGMP Leave Group command since it        is directed on an administratively scoped address;    -   42. IPMS 120 receives the IGMP Leave Group command, verifies it        has no other Clients in Group Address=239.216.0.8 (using IGMP        Query), and immediately stops transmission of 239.216.0.8        multicast.

The following handshake operations occur during final termination:

-   -   43. Client A sends a UDP packet (Destination IP        Address=128.0.0.255, Port=255) to the IPMS 120    -   44. Access Switch/Router #1 forwards UDP packet to backbone;    -   45. Gateway Router ignores the message since it is routed        locally;    -   46. IPMS 120 receives the IDP packet and sends a UDP packet        (Destination IP Address=128.0.0.1, Port=255) to Client A;    -   47. Gateway Router ignores message routed locally;    -   48. Access Switch/Router #1 forwards the UDP packet to Client A;    -   49. Client A receives UDP packet.

ISP Model 5—ISP with Multiple LAN Segments/Multicast StreamsSegmented—Scenario 2

In the example of FIG. 25. Client A and the IPMS 120 first joinMulticast Group 239.216.63.240 to establish a mechanism for sendingmulticast control messages to each other. Next, Client A joins,receives, and leaves Multicast Group 239.216.63.248 to receive a briefmulticast from the IPMS 120. After that, Client A joins and receivesMulticast Group 239.216.0.8. Then, network elements query the group sothat multicast traffic can be pruned in the event group members silentlyleave the group. Finally, Client A leaves Multicast Group 239.216.0.8.

The IPMS 120 filters the multicast streams sent to each segment so thatonly multicast addresses which are currently “joined” will be sent tothe LAN Switch per segment. This implies that the LAN switch does nothave to support IGMP V2, although this provision is not mandatory.

In the scenario of FIG. 25, the following assumptions have been made:

-   -   IPMS 120 IP Address=128.0.0.255, Client A IP Address=128.0.0.1;    -   All IP Multicast Addresses transmitted by the IPMS 120 are        “Administratively Scoped” addresses in the range 239.216.0.0        through 239.219.255.255 (addresses 239.216.0.8, 239.216.63.240,        239.216.63.248 used in this example);    -   Access Switch/Routers and IPMS 120 support IGMP V2;    -   LAN Switch may or may not support IGMP V2;    -   LAN Switch configuration:        -   Virtual LAN#1=LAN Segment #1, Backbone, IPMS 120 Control,            Filtered Stream#1;        -   Virtual LAN#2=LAN Segment #2. Backbone, IPMS 120 Control,            Filtered Stream#2    -   Remote Router does not forward IGMP messages with        “Administratively Scoped” Multicast addresses (this includes        messages with Dest IP=239.*.*.*, and IGMP messages with Dest        IP=224.0.0.1/224.0.0.2 that specify a Group Address=239.*.*.*);    -   The IPMS 120 and the Clients use Multicast        Address=239.216.63.240 to pass proprietary UDP packets using UDP        Port=255.

The following operations occur during initial handshake in the system:

-   -   1. IPMS 120 sends an IOMP V2 Membership Report (Destination IP        Address=239.216.63.240, Group Address=239.216.63.240);    -   2. LAN Switch receives IOMP V2 Membership Report, forwards the        message, and adds the IPMS 120 to the Groups the 239.216.63.240        multicast being used for multicast control messages;    -   3. Gateway Router does not forward the administratively scoped        membership report to the Internet;    -   4. Client A sends an IGMP V2 Membership Report (Destination IP        Address=239.216.63.240, Group Address=239.216.63.240);    -   5. Access Switch/Router #1 forwards IGMP V2 Membership Report to        LAN Segment #1 (assuming it has no other interfaces in Group        Address=239.216.63.240);    -   6. LAN Switch receives IGMP V2 Membership Report, forwards the        message, and adds Client A to the Group;    -   7. Gateway Router does not forward the administratively scoped        membership report to the Internet;    -   8. IPMS 120 receives IGMP V2 Membership Report, the        239.216.63.240 multicast being used for multicast control        messages;    -   9. Client A sends an IGMP V2 Membership Report (Destination IP        Address=239.216.63.248, Group Address=239.216.63.248);    -   10. Access Switch/Router #1 forwards IGMP V2 Membership Report        to LAN Segment #1 (assuming it has no other interfaces in Group        Address=239.216.63.248);    -   11. LAN Switch receives IGMP V2 Membership Report and forwards        the message;    -   12. Gateway Router does not forward the administratively scoped        membership report to the Internet;    -   13. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.63.248 multicast out NIC#2 and NIC#3 onto Filtered        Streams 1 and 2—the data payload of the 239.216.63.248 multicast        includes the IPMS 120 IP Address, and a test pattern;    -   14. If LAN Switch is IGMP V2 enabled, it will forward        239.216.63.248 multicast to LAN Segment #1 only. If it isn't,        then the 239.216.63.248 multicast will be forwarded to both LAN        Segment #1 and LAN Segment #2;    -   15. Access Switch/Router #1 forwards 239.216.63.248 multicast to        Client A only;    -   16. Client A receives IPMS 120 IP Address and test pattern and        then sends an IGMP Leave Group (Destination IP Address=224.0.0.2        Group Address=239.216.63.248);    -   17. Access Switch/Router #1 receives IGMP Leave Group, verifies        it has no other interfaces in Group Address239.216.63.248 (using        IGMP Query), forwards IGMP Leave Group to LAN Segment #1, and        immediately stops forwarding the 239.216.63.248 multicast to        Client A;    -   18. LAN Switch receives the IGMP Leave Group and forwards the        message. If it is IGMP V2 enabled, it will verify it has no        other LAN Segment #1 Clients in Group Address=239.216.63.248        (using IGMP Query), and immediately stop transmission of        239.216.63.248 multicast to LAN Segment #1;    -   19. Gateway Router ignores IOMP Leave Group since it is on an        administratively scoped address;    -   20. IPMS 120 receives IGMP Leave Group, verifies it has no other        Clients in Group Address=239.216.63.248, and immediately stops        transmission of the 239.216.63.248 multicast;    -   32. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.0.8 multicast out NIC#2 onto Filtered Stream #1;    -   33. LAN Switch forwards 239.216.0.8 multicast to LAN Segment #1        only;    -   34. Access Switch/Router #1 forwards 239.216.0.8 multicast to        Client A only;    -   35. Client A receives 239.216.0.8 multicast.

The following query operations occur to ensure that the IPMS does notunnecessarily provide a Group multicast transmission when there are nosubscribers:

-   -   36. Access Switch/Router #1 sends IGMP Group-Specific Query        (Destination IP Address=239.216.0.8, Group Address=239.216.0.8)        to Client A;    -   37. If Access Switch/Router #1 receives an IGMP V2 Membership        Report (Destination IP Address=239.216.0.8, Group Address        239.216.0.8), do nothing;    -   38. If there is no Membership Report, then Access Switch/Router        #1 sends IGMP Leave Group (Destination IP Address=224.0.0.2,        Group Address=239.216.0.8) to LAN Segment #1 and immediately        stops forwarding the 239.216.0.8 multicast to all clients        (including Client A), operations then proceed from Step 53;    -   39. IPMS 120 sends UDP packet(Destination IP        Address=239.216.63.240, Port=255) from NIC #1;    -   40. If LAN Switch is IGMP V2 enabled, it will forward the packet        to all interfaces currently monitoring the 239.216.63.240        stream. If it is not IGMP V2 enabled, the packet will be        forwarded to all LAN interfaces.    -   41. Gateway Router will ignore the administratively scoped        packet;    -   42. Access Switch/Routers will forward the packet to all Clients        listening to the 239.216.63.240 stream;    -   43. Client A will respond with a UDP packet (Destination IP        Address=239.216.63.240, Port=255);    -   44. The packet will be forwarded by Access/Switch Router #1 to        LAN Segment #1;    -   45. The LAN Switch will forward the packet to the IPMS 120 NIC        #1;    -   46. Gateway Router will ignore the administratively scoped        packet;    -   47. If IPMS 120 receives no UDP response, then it immediately        stops forwarding the 239.216.0.8 to all Clients (group is left        due to no response); Independently, if the LAN Switch is IGMP V2        enabled, the following operations occur:    -   48. LAN Switch sends IGMP Group-Specific Query (Destination IP        Address=239.216.0.8, Group Address=239.216.0.8) to LAN Segment        #1;    -   49. If LAN Switch receives IGMP V2 Membership Report        (Destination IP Address=239.216.0.8, Group Address=239.216.0.8),        do nothing    -   50. If there is no Membership Report then LAN Switch sends IGMP        Leave Group (Destination IP Address=224.0.0.2, Group        Address=239.216.0.8) to IPMS 120 and immediately stops        transmission of 239.216.0.8 multicast to LAN Segment #1 (group        is left due to no response);

The following operations occur when Client A leaves Group Address239.216.0.8:

-   -   51. Client A sends an IGMP Leave Group(Destination IP        Address=224.0.0.2, Group Address=239.216.0.8):    -   52. Access Switch/Router #1 receives IGMP Leave Group, verifies        it has no other interfaces in Group Address=239.216.0.8 (using        IGMP Query), forwards IGMP Leave Group to LAN Segment #1, and        immediately stops forwarding the 239.216.0.8 multicast to Client        A;    -   53. LAN Switch receives IGMP Leave Group and forwards the        message. If it is IGMP V2 enabled it verifies it has no other        LAN Segment #1 Clients in Group address 239.216.0.8 (using IGMP        Query), and immediately stops transmission of 239.216.0.8        multicast to LAN Segment 1:    -   54. Gateway Router ignores IGMP Leave Group since it is in an        administratively scoped address packet;    -   55. IPMS 120 receives IGMP Leave Group, verifies it has no other        Clients in Group Address=239.216.0.8, and immediately stops        transmission of 239.216.0.8 multicast.

The following termination handshake operations occur upon termination ofthe multicast subscription:

-   -   56. Client A sends a UDP packet (Destination IP        Address=128.0.0.255. Port=255) to the IPMS 120:    -   57. Access Switch/Router #1 forwards UDP packet to LAN Segment        #1:    -   58. LAN Switch forwards packet to IPMS 120 NIC #1;    -   59. IPMS 120 receives UDP packet and sends a UDP packet        (Destination IP Address=28.0.0.1, Port255) to Client A;    -   60. LAN Switch forwards packet to LAN Segment #1;    -   61. Gateway Router will ignore the administratively scoped        packet;    -   62. Access Switch/Router #1 forwards packet to Clients A;    -   63. Client A receives UDP packet.

ISP Model 6—Large ISP with Affiliated ISP—Scenario 2

In the example of FIG. 26, Remote Client H and the IPMS 120 first joinMulticast Group 239.216.63.240 to establish a mechanism for sendingmulticast control messages to each other. Next, Remote Client H joinsreceives, and leaves Multicast Address 239.216.63.248 to receive a briefmulticast from the IPMS 120. After that, Client H joins and receivesMulticast Group 239.216.0.8. Then, network elements query the group sothat multicast traffic can be pruned in the event group members silentlyleave the group. Finally, Client H leaves Multicast Group 239.216.0.8.

The IPMS 120 filters the multicast streams sent to each segment so thatonly multicast addresses that are currently “joined” will be sent to theLAN Switch per segment. This implies that the LAN switch does not haveto support IGMP V2, although this is not necessary. The LAN Switch mayfilter the multicast stream sent to each segment so that only multicastaddresses which are currently “joined” by plans on a segment will beplaced on the segment. For the Remote ISP the multicast streamspreferably to not use bandwidth on the Router link to the ISP (to avoidimpacting normal Internet traffic). Rather, a bridged connection is usedto send the streams to the Remote ISP. The only segments that receivethe multicast streams are LAN Segment #1 and the bridged connection tothe Remote ISP that is considered to be LAN Segment #2.

In this scenario, the following assumptions have been made:

-   -   IPMS 120 IP Address 28.0.0.255, Client A IP Address=128.0.0.1;    -   All IP Multicast Addresses transmitted by the IPMS 120 are        “Administratively Scoped” addresses in the range 239.216.0.0        through 239.219.255.255 (addresses 239.216.0.8, 239.216.63.240,        239.216.63.248 used in this example);    -   Access Switch/Router and IPMS 120 support IGMP V2;    -   LAN Switch may or may not support IGMP V2;    -   LAN Switch configuration:        -   Virtual LAN#1 LAN Segment #1 Backbone, IPMS 120 Control,            Filtered Stream#1;        -   Virtual LAN#2=LAN Segment #2, IPMS 120 Control, Filtered            Stream#2;        -   Virtual LAN#3 LAN Segment #3, Backbone;    -   LAN Bridge configuration: Only forward        239.216.0.0-239.219.255.255; 224.0.0.1, 224.0.0.2;    -   Remote Router does not forward IGMP messages with        “Administratively Scoped” Multicast addresses (this includes        messages with Dest IP239.*.*.*, and IGMP messages with Dest        IP=224.0.0.1/224.0.0.2 that specify a Group Address=239.*.*.*);    -   The IPMS 120 and the Clients use Multicast        Address=239.216.63.240 to pass UDP packets using UDP Port=255.

In this scenario, the followings initial handshake operations takeplace:

-   -   1. IPMS 120 sends an IGMP V2 Membership Report (Destination IP        Address=39.216.63.240. Group Address=239.216.63.240);    -   2. LAN Switch receives IGMP V2 Membership Report, forwards the        messages and adds the IPMS 120 to the Group, the 239.216.63.240        multicast being used for multicast control messages;    -   3. Gateway Router does not forward the administratively scoped        membership report to the Internet;    -   4. Client H sends an IGMP V2 Membership Report (Destination IP        Address=239.216.63.240, Group Address=239.216.63.240);    -   5. Access Switch/Router #1 forwards IGMP V2 Membership Report to        LAN Segment#1 (assuming it has no other interfaces in Group        Address=239.216.63.240);    -   6. LAN Switch receives IGMP V2 Membership Report, forwards the        message, and adds Client H to the Group;    -   7. Gateway Router does not forward the administratively scoped        membership report to the Internet;    -   8. IPMS 120 receives IGMP V2 Membership Report the        239.216.63.240 multicast being used for multicast control        messages;    -   9. Client H sends an IGMP V2 Membership Report (Destination IP        Address=239.216.63.248, Group Address=239.216.63.248);    -   10. Access Switch/Router #2 forwards IGMP V2 Membership Report        to Remote Backbone (assuming it has no other interfaces in Group        Address=239.216.63.248);    -   11. LAN Bridge forwards IGMP V2 Membership Report;    -   12. Remote Router ignores the administratively scoped IGMP V2        Membership Report;    -   13. LAN Switch receives IGMP V2 Membership Report, forwards the        message, and enables transmission of 239.216.63.248 multicast to        LAN Segment #2;    -   14. IPMS 120 receives IGMP V2 Membership Report and transmits        239.216.63;248 multicast out NIC#2 and NIC#3 onto Filtered        Streams 1 and 2—the data payload of the 239.216.63.248 multicast        includes the IRMS 120 IP Address, and a test pattern;    -   15. If LAN Switch is IGMP V2 enabled, it will forward        239.216.63.248 multicast to LAN Segment #2 only. If it is not so        enabled, then the 239.216.63.248 multicast data will be        forwarded to both LAN Segment #1 and LAN Segment #2;    -   16. LAN Bridge forwards the 239.216.63.248 multicast data;    -   17. Access Switch/Router #2 forwards 239.216.63.248 multicast to        Client H only;    -   18. Remote Router ignores 239.216.63.248 multicast data;    -   19. Client H receives the IPMS 120 IP Address and test pattern        and then sends an IGMP Leave Group (Destination IP        Address=224.0.0.2. Group address=239.216.63.248);    -   20. Access Switch/Router 2 receives IGMP Leave Group, verifies        it has no other interfaces in Group Address=239.216.248 (using        IGMP Query), forwards IGMP Leave Group to LAN Bridge, and        immediately stops forwarding the 239.216.63.248 multicast to        Client H;    -   21. LAN Bridge forwards the IGMP Leave Group command;    -   22. Remote Router ignores the administratively scoped IGMP Leave        Group command;    -   23. LAN Switch receives IGMP Leave Group and forwards the        message. If it is IGMP V2 enabled, it will verify it has no        other LAN Segment #2 Clients in Group address=239.216.63.248        (using IGMP Query), and will immediately stop transmission of        the 239.216.63.248 multicast to LAN Segment #2;    -   24. IPMS 120 receives the IGMP Leave Group command, verifies it        has no other Clients in Group Address=239.216.63.248, and        immediately stops transmission of the 239.216.63.248 multicast        data;    -   25. Client H sends a UDP packet (Destination IP        Adress=128.0.0.255, Port=255) to the IPMS 120;    -   26. Access Switch/Router #2 forwards a UDP packet to the        backbone of the remote ISP;    -   27. LAN Bridge forwards the IGMP V2 Membership Report;    -   28. Remote Router ignores the administratively scoped IGMP V2        Membership Report;    -   29. LAN Switch forwards the UDP packet to the IPMS 120 control        stream (NIC #1);    -   30. IPMS 120 receives UDP packet and sends UDP packet response        (Destination IP Address=128.0.0.1, Port=255) from NIC #1;    -   31. LAN Switch forwards the UDP packet to the LAN Segment #2        since the packet is addressed to Client H;    -   32. Access Switch/Router #2 forwards UDP packet to Client H;    -   33. Client H receives UDP packet.

The following operations occur when Client H joins Multicast Group239.216.0.8;

-   -   34. Client H sends an IGMP V2 Membership Report (Destination IP        Address=239.216.0.8, Group Address=239.216.08);    -   35. Access Switch/Router #2 forwards IGMP V2 Membership Report        to Remote Backbone (assuming it has no other interfaces in Group        Address=239.216.0.8);    -   36. LAN Bridge forwards IGMP V2 Membership Report;    -   37. Remote Router ignores the administratively scoped IGMP V2        Membership Report;    -   38. LAN Switch receives IGMP V2 Membership Report and forwards        the message. If it is IGMP V2 enabled, it will enable        transmission of 239.216.0.8 multicast to LAN segment #2;    -   39. IPMS 120 receives the IGMP V2 Membership Report and        transmits the 239.216.0.8 multicast through NIC #3 onto Filtered        Stream #2;    -   40. LAN Switch forwards 239.216.0.8 multicast to LAN Segment #2        only;    -   41. LAN Bridge forwards the 239.216.0.8 multicast data;    -   42. Access Switch/Router #2 forwards 239.216.0.8 multicast data        to Client H only;    -   43. Remote Router ignores 239.216.0.8 multicast data;    -   44. Client H receives 239.216.0.8 multicast.

The following query operations also take place to ensure thatunnecessary multicast data is not transmitted over any LAN:

-   -   45. Access Switch/Router #2 sends IGMP Group-Specific Query        (Destination IP Address=239.216.0.8, Group Address=239.216.0.8)        to Client H;    -   46. If Access Switch/Router #2 receives an IGMP V2 Membership        Report (Destination IP Address=39.216.0.8, Group        Address=239.216.0.8), do nothing:    -   47. If there is no Membership Report, then Access Switch/Router        #2 sends an IOMP Leave Group command (Destination IP        Address=224.0.0.2, Group Address=39.216.0.8) to the backbone of        the remote ISP and immediately stops forwarding the 239.216.0.8        multicast data to Client H; operations then proceed from Step 63        below;    -   48. IPMS 120 sends UDP packet (Destination IP        Address=239.216.63.240, Port=255) from NIC #1;    -   49. If LAN Switch is IGMP V2 enabled, it will forward the packet        to all interfaces currently monitoring the 239.216.63.240 stream        if it is not IGMP V2 enabled, the packet will be forwarded to        all LAN interfaces    -   50. Access Switch/Routers forwards the packet to all Clients        listening to the 239.216.63.240 stream;    -   51. Client H responds with a UDP packet (Destination IP        Address=239.216.63.240, Port=255);    -   52. Access/Switch Router #2 forwards the packet to the backbone        of the remote ISP;    -   53. LAN Bridge forwards packet;    -   54. Remote Router ignores packet;    -   55. The LAN Switch forwards packet to the IPMS 120 NIC #1;    -   56. If IPMS 120 does not receive a UDP response, then it        immediately stops forwarding the 239.216.0.8 to all Clients        (group is left due to no response). If the LAN Switch is IGMP V2        enabled, the following operations will take place;    -   57. LAN Switch sends IGMP Group-Specific Query (Destination IP        Address=239.216.0.8, Group Address=239.216.0.8) to LAN Segment        #2;    -   58. LAN Bridge forwards IGMP Group-Specific Query;    -   59. If LAN Switch receives an IGMP V2 Membership Report        (Destination IP Address=239.216.0.8, Group Address=239.216.0.8),        then do nothing;    -   60. If there is no Membership Report, then LAN Switch        immediately stops transmission of 239.216.0.8 multicast to LAN        Segment #2 (group is left due to no response).

The following operations take place when Client H leaves Multicast Group239.216.0.8:

-   -   61. Client H sends an IGMP Leave Group command (Destination IP        Address=224.0.0.2, Group Address=239.216.0.8);    -   62. Access Switch/Router #2 receives the IGMP Leave Group        command. verifies it has no other interfaces in Group        Address=239.216.0.8 (using IGMP Query), forwards the IGMP Leave        Group to the backbone of the remote ISP, and immediately stops        forwarding the 239.216.0.8 multicast data to Client H;    -   63. LAN Bridge forwards IGMP Leave Group command;    -   64. Remote Router ignores the administratively scoped IGMP Leave        Group command;    -   65. LAN Switch receives the IGMP Leave Group command and        forwards the message: if it is IGMP V2 enabled, it verifies it        has no other LAN Segment #2 Clients in Group Address=239.216.0.8        (using IGMP Query), and immediately stops transmission of        239.216.0.8 multicast to LAN Segment #2;    -   66. IPMS 120 receives the IGMP Leave Group command, verifies it        has no other Clients in Group Address=239.216.0.8, and        immediately stops transmission of the 39.216.0.8 multicast.

The following termination handshake operations also take place:

-   -   67. Client H sends a UDP packet (Destination IP        Address=128.0.0.255. Port=255) to the IPMS 120;    -   68. Access Switch/Router #2 forwards the LTDP packet to the        backbone of the remote ISP;    -   69. LAN Bridge forwards the packet;    -   70. Remote Router ignores the packet;    -   71. LAN Switch forwards the packet to IPMS 120 NIC #1;    -   72. IPMS 120 receives the UDP packet and sends a UDP packet        (Destination IP Address=128.0.0.1, Port=255) to Client H;    -   73. LAN Switch forwards the packet to LAN Segment #2 only;    -   74. LAN Bridge forwards the packet;    -   75. Access Switch/Router #2 forwards the packet to Client H        only; and    -   76. Client H receives the UDP packet.

If remote clients join “normal” multicast groups through the remoterouter, the 224.0.0.1 and 224.0.0.2 IGMP V2 messages will be bridged tothe LAN Switch. The LAN Switch will forward the IGMP messages throughLAN segment #2 to the IPMS 120. The IPMS 120 will ignore the messagesissued for a non-existent stream.

FIG. 27 shows a basic ISP configuration. The Internet is connected to aninternal 10 BaseT LAN. This internal LAN has a local file server that isused for locally served Web pages. Also on this LAN is connected aremote access server (modem pool) which is used to Connect the ISPcustomers via the LEC (local exchange carrier—the local phone company)to the Internet.

FIG. 28 shows how this ISPO grows to serve more customers. A layer 3switch is added to the Internal ISP LAN. This LAN is usuallyinterconnected by 100 BaseT added to the internal ISP LAN. This LAN isusually interconnected by 100 BaseT or FDDI transmission technology. Theswitch is used to interconnect multiple 10 BaseT LAN segments to the ISPLAN. Each of these segments have multiple remote access servers that areused to connect users to the Internet.

FIG. 29 shows how broadband multimedia data is inserted into an ISPusing the ideas described in this application. This configuration takesadvantage of current ISP architectures. Many ISP's today have evolvedover time as shown in FIG. 27 and FIG. 28. They started with one remoteaccess router serving a few customers (FIG. 27) and have expanded tomultiple remote access routers (FIG. 28). FIG. 29 shows the addition ofmultiple satellite receivers that receive multicast data.

In this configuration, the Layer 3 IP switch performs several functions.The first function is to connect the proper multicast stream form theappropriate satellite receiver to the appropriate LAN segments. Thisrequires the switch to implement the IP Multicast Protocol (RFC1112).

The second function is to connect the proper Internet traffic to theappropriate LAN segment.

The third function of the Layer 3 switch is to perform the IOMP querierfunction as specified in RFC1112.

If the existing Layer 3 switch meets the above requirements, then it canbe used. If not, then the ISP must upgrade the switch with one thatmeets these requirements. The commercially available HP800T switch isone example of such a layer 3 multicast enabled switch.

Such a configuration has the advantage of simplicity since the satellitereceiver only needs to strip the HDLC (or other) encapsulation from theincoming data and electrically convert the data to the ethernet format.It does not need to have any knowledge of IP multicasting protocols.

Enhancements that could be incorporated in the receiver could bemulticast address translation and data de-scrambling. In this case, thereceiver must understand the IP multicasting protocol to perform theseappropriate functions.

FIG. 30 illustrates the layout of an exemplary traditional web page 800suitable for use in the present multicast system. As illustrated, theweb page 800 includes a video display window 800 that accepts anddisplays a video data stream from the broadcast transmission. Externalto the video display window 800, text, and graphic content relating tothe content of the video is displayed. Such content can be provided inthe broadcast transmission itself, over the backbone of the Internet, orfrom storage at the ISP.

The web page 800 is also provided with a plurality of baud rateselection buttons 810, 815, 820, and 825. Each button corresponds to abaud rate of a broadcast video stream, each stream having the samemultimedia content. For example, button 810 may correspond totransmission of the media content for the display window 800 at 14.4K.Similarly, buttons 815, 820, and 825 may correspond to baud rates of28.8 K. 56.6 K. and 1.5 MB, respectively. This allows the client toselect a baud rate for the video transmission rate that is suited to hissystem.

The web page provides substantial information and versatility to theuser. The user may be presented with a substantially continuous flow ofvideo information while concurrently having text and other informationpresented to him that may or may not be related to the video to allowthe user to select other web pages, audio information, further videocontent, etc. These further selections may relate to the particulartopic. product, etc., provided in the video content. The user may begiven an option to select multiple video channels that may be suppliedconcurrently. The user is provided with a substantial number of channelsto choose from, thereby allowing the user to select the desired videocontent.

The web pace needed not necessarily be provided with buttons for theselection of baud rate. Rather, a software plug-in for the web browserused by the client may be used to automatically join the appropriatemulticast group depending on the data rate at which the clientcommunicates with the ISP. In such instances, the plug-in software firstdetects the data rate at which the client is communicating with theInternet service provider. When a client wishes to view a particularvideo stream content, the software compares this detected data rateagainst a table of different data rates for the same content, each datarate corresponding to a unique multicast Group address. The softwarejoins the client to the multicast group having the maximum data ratethat does not exceed the data rate at which the software detected thecommunications between the client and the Internet service provider.

An exemplary embodiment of software that may be used for this purpose isset forth in an “Appendix A”, filed with related application Ser. No.08/969.164, now U.S. Pat. No. 6,101,180, the entire contents of which isincorporated by reference herein. Appendix A includes listings ofsoftware source code in C++ for automatically detecting the baud rate atwhich the client is connected to the system and selecting the propermulticast join group.

Numerous modifications can be made to the foregoing system withoutdeparting from the spirit and scope of the various inventive aspects ofthis invention as set forth in the appended claims. Therefore, it is theintention of the inventors to encompass all such chances andmodifications that fall within the scope of the appended claims.

1. A method of transmitting digital content to a plurality of separateusers accessing Internet services at least in part via conventionaltwo-way Internet protocol (IP) connection, said digital contentcomprising digital data and/or digital audio and/or digital video, themethod comprising the steps of: a) formatting said digital content inaccordance with an IP protocol to generate IP digital data; b) providinga streaming transmission of the IP digital data from a transmission siteto a remote Internet point of presence of an Internet service provider(ISP) through one or more substantially one-way data flow bandwidthportions of a digital communications medium that is substantiallyunaffected by conventional two-way IP Internet communications traffic;c) multicastiag the IP digital data transmitted by step (b) from theremote Internet point of presence to a plurality of separate receivingInternet user apparatus connected to but distant from the remoteInternet point of presence; and d) contemporaneously with step c),transmitting relatively time-insensitive additional IP digital data viaa conventional two-way IP connection that is separate from the one-waydata flow bandwidth portions to the remote Internet point of presenceand then to the plurality of separate receiving Internet user apparatus;wherein, on each among the plurality of separate receiving Internet userapparatus, received IP digital data multicast by step (c) and receivedadditional IP digital data transmitted by step (d) is processed to allowsimultaneous use of both.
 2. A method of providing digital content to aplurality of disparate users accessing Internet services at least inpart via conventional two-way Internet protocol (IP) connection, saiddigital content comprising digital data and/or digital audio and/ordigital video, the method comprising the steps of: a) formatting saiddigital content in accordance with an IP protocol to produce IP digitaldata; b) providing a streaming transmission of the IP digital data froma transmission site to a distant routing station at an internet serviceprovider's internet point of presence through one or more substantiallyone-way data flow bandwidth portions of a digital communications mediumthat is substantially unaffected by conventional two-way IP Internetcommunications traffic; and c) providing, from the Internet serviceprovider's Internet point of presence, multicast access of said IPdigital data received via streaming transmission at the Internet serviceprovider's Internet point of presence by step (b) to said plurality ofdisparate users accessing Internet services via two-way IP connection.3. The method of claim 2 wherein one or more of said substantiallyone-way data flow bandwidth portions comprise one or more video contentchannels.
 4. The method of claim 2 wherein one or more of thesubstantially one-way data flow bandwidth portions comprise one or moreaudio content channels.
 5. The method of claim 2 further including thestep of receiving and processing at least one IP request from at leastone of said separate users.
 6. The method of claim 2 wherein themulticast access service provided in step c) is localized to apredetermined geographic region.
 7. The method of claim 2 wherein thedigital communications medium substantially unaffected by conventionaltwo-way IP Internet communications traffic comprises, at least in part,an extraterrestrial satellite communications system.
 8. The method ofclaim 2 wherein the digital communications medium substantiallyunaffected by conventional two-way IP Internet communications traffic isa substantially terrestrial communications system.
 9. The method ofclaim 2 wherein the digital communications medium substantiallyunaffected by conventional two-way IP Internet communications traffic isa reserved portion of a commercial IP communications network.
 10. Amethod of providing digital streaming content to a plurality ofdisparate users accessing Internet services at least in part viaconventional two-way Internet protocol (IP) connections, the streamingdigital content comprising digital data and/or digital audio and/ordigital video, the method comprising the steps of: a) transmitting thedigital streaming content from a transmission site to a distant routingstation at an Internet service provider's Internet point of presencethrough one or more substantially one-way data flow bandwidth portionsof a digital communications medium that is substantially unaffected byconventional two-way IP Internet communications traffic; and b)providing, from the Internet service provider's Internet point ofpresence, access to the digital streaming content received at theInternet service provider's Internet point of presence via step (a), bymulticast transmission to said plurality of disparate users accessingInternet services via two-way IP connection.
 11. A method of providingaccess to multicast digital content to a plurality of disparate usersaccessing Internet services at least in part via two-way Internetprotocol (IP) connections, the digital content comprising digital dataand/or digital audio and/or digital video information, the methodcomprising the steps of: a) transmitting the digital data from atransmission site to a distant routing station at an Internet serviceprovider's Internet point of presence through one or more substantiallyone-way data flow bandwidth portions of a digital communications datatransport service or transmission medium that effectively bypassescongested portions of the Internet and remains substantially unaffectedby IP Internet communications traffic; b) receiving the digital data,transmitted by step (a), at said routing station; and c) providingaccess to the digital data by multicast transmission delivery from saidInternet point of presence to said plurality of disparate usersaccessing Internet services via two-way IP connection.
 12. A method oftransmitting digital data, said digital data comprising streaming and/ornon-streaming data encompassing both video and audio informationcontent, to a plurality of disparate Internet users accessing Internetservices at least in part via conventional two-way Internet protocol(IP) connection, the method comprising the steps of: a) transmitting thedigital data to at least one distant Internet point of presence of anInternet service provider through one or more substantially one-way dataflow bandwidth portions of a digital communications medium that isdisparate from and substantially unaffected by conventional two-way IPInternet communications traffic; and b) multicast transmitting thedigital data from said at least one distant Internet point of presenceto said plurality of disparate Internet users over a two-way IP networkconnecting said at least one Internet point of presence to saiddisparate Internet users, wherein at least one or more of said pluralityof disparate Internet users employ digital communications equipment thatutilizes an Internet browser program or its equivalent to accessInternet services.
 13. The method of claim 12 wherein said digitalcommunications equipment comprises a display device and said Internetbrowser program or its equivalent used by said plurality of disparateInternet users for accessing Internet services provides a screen displaywherein at least a first portion of the display device screen isallocated for displaying the digital data received from said at leastone distant Internet point of presence and wherein a separate portion ofthe display device screen is allocated for simultaneously conductingtwo-way interactive IP connectivity.
 14. The method of claim 12 whereinone or more of said one-way data flow bandwidth portions comprise aone-way wireless transmission system.
 15. The method of claim 12 whereindie transmitting of step a) comprises transmitting the digital data toplural Internet points of presence, including said at least one distantInternet point of presence, substantially through a reserved one-waydata flow bandwidth portion.
 16. The method of claim 12 wherein thetwo-way IP network comprises a telecommunications network.
 17. Themethod of claim 12 wherein the two-way IP network comprises a cablenetwork.
 18. The method of claim 12 wherein the two-way IP networkcomprises a local area computer network.
 19. The method of claim 16wherein the telecommunications network includes a POTS line connectingcommunications equipment supporting said Internet browser program or itsequivalent used by at least one of said plurality of disparate Internetusers to said at least one distant Internet point of presence, whereinsaid line at browser may access and display said digital datatransmitted via said one-way data flow bandwidth portions.
 20. A methodof providing localized multicast access to streaming digital content,said digital content comprising digital data and/or audio and/or videoinformation, by a plurality of disparate Internet users accessing theInternet at least in part via conventional two-way Internet protocol(IP) connection, the method comprising the steps of: providing astreaming transmission of digital content from a head-end content sourcethrough one or more substantially one-way data flow bandwidth portionsof a communications medium that is disparate from and substantiallyunaffected by Internet communications traffic to at least one distantInternet point of presence of an Internet service access provider thatprovides IP digital data to one or more users via conventional two-wayIP connections; and distributing the streaming digital content viamulticast transmission to said plurality of disparate Internet usersthat access and/or utilize the multicast streaming digital contentreceived from the Internet service access provider via two-way IPconnection.
 21. The method of claim 20 wherein the distributing ofstreaming digital content via multicast transmission from to an Internetpoint of presence is localized to a predetermined geographic region.